iraf.net

>From forsstro@cc.helsinki.fi Fri Nov 15 06:22:00 1996
From: Vivan M Forsstrom <forsstro@cc.helsinki.fi>
To: Mike Fitzpatrick <fitz@noao.edu>
Cc: sites@noao.eduHi Mike,On Thu, 14 Nov 1996, Mike Fitzpatrick wrote:
> to check against 6 instead of 5. Do the same thing in the irafuser.csh script
> and explicitly set the MACH variable to be 'irix' instead of using the uname
> command. With that done resource the irafuser.csh and run the install script
> again.Thank you again for a quick reply. Installation script ran OK, thank you.
But another day, more questions. Cl runs now ok as iraf without any error
notices once I located a few places in hlib where the package checks
against os 5. As myself mkiraf was found, but obviously there's still
somewhere similar definitions, because then cl crashes sayingsirius 2% cl
/appl2/iraf/iraf/bin.f68881/cl.e - Command not found But where?>We plan to upgrade our system to IRIX 6 for the V2.11 release, I'm
>surprised nobody's asked us about this before. Let us know if you have any
> other problems or questions. Others may have done the changes without checking with you first. I
believe I'll ask a few questions after this still once I progress with
the installation.Vivan"Many and strange are the universes that drift like bubbles in the foam
upon the River of Time" -A. C. Clarke>From fitz Fri Nov 15 12:59:00 1996
To: forsstro@cc.helsinki.fi
Subject: Re: iraf and irix6.2 install problemHi Vivan,
The 'cl' command is created by the install script as a symbolic
link to hlib$cl.csh. This script is what builds up the path to the cl.e
executable, from your error it's somehow got the idea that IRAFARCH is set
in your environment to 'f68881'. The cl.csh script uses the uname command
to set the MACH variable (on your system this becomes 'irix64') but at the
bottom of the script where it determines the architecture this should still
fall back to setting IRAFARCH to 'irix', is the script different on your
machine? Is it possible you've got something in your .cshrc/.login that
might be setting IRAFARCH (or sourcing some file that does)? To track this
down you might try starting with "csh -x $iraf/unix/hlib/cl.csh" to see
how the script executes and where the f68881 is coming from. Hope this
helps.Cheers,
-Mike