Finishing installation on Mac OSX

[qroper224]

Hello,

I'm installing IRAF on MacOS-X and followed the cookbook supplied in
pciraf.ps all the way through the ./install phase and IRAF was
"installed successfully". However, I'm not sure what to do next. The
pciraf.ps document says that when logged in as iraf that I should be
able to run iraf simply by typing cl since iraf should be able to run
given the login files included with the system. However, an error of
-bash: cl: command not found
which appears that I'm missing some aliasing perhaps. Furthermore, when
logged in as another user the mkiraf command does not initiate the
initialization of their iraf profile but instead returns a similar error
-bash: cl: command not found
which again looks like there's something amiss in my .bash_profile
file. Could you please advise on how to finish this install?

Thanks,
Quentin

[fitz]

'Command not found' usually indicates a path problem. By default, the iraf commands are created as links in the /usr/local/bin directory, this directory must be in the PATH variable you specify in your .bash_profile. Less often, the path is correct but the links are bad because the 'iraf root directory' was specified incorrectly (or is overridden in your environment). The install script should have caught this last case, so check your path first.

-Mike

[qroper224]

I figured the problem was something to that effect, but I'm not sure where the command mkiraf is to alias to in my bash profile. Where is the mkiraf command installed?

I did end up finding the cl.e file in the usr/local/iraf/irafbin/bin.macintel folder-- should I copy this to usr/local/bin for simplicity? When I run it, it gives me a half-dozen error messages of the tune "cannot open "/usr/include/iraf.h". What does this mean?

Thanks again.

[fitz]

Sounds like the install script wasn't actually run, did you by chance run it as "install -n" (where -n is the no-op flag) or without a 'sudo' ?? The key is the missing /usr/include/iraf.h. Otherwise, all commands like 'mkiraf' and 'cl' are put in the same directory (normally, /usr/local/bin but you can specify someplace else). The 'cl' command has to do some environment setup, copying the cl.e binary directly is not recommended.

Try re-running the install script as