ERROR: No /iraf/iraf//bin.linux64/vocl.e binary found
ddayjuno wrote on Sep 01, 2016
I have downloaded and installed iraf according to the instructions here: http://www.astronomy.ohio-state.edu/~khan/iraf/iraf_step_by_step_installation
It seems to have installed fine - didn't show any errors during installation and d9&xgterm are running fine. But when I try to run iraf using cl, I just get:
ERROR: No /iraf/iraf//bin.linux64/vocl.e binary found
Checking the file path in the error, there's an extra backslash b/n iraf & bin.linux64, and regardless, I don't actually have that specified directory. The proper path seems like it should be /iraf/iraf/bin.linux/vocl.e
Any suggestions how to fix this?
Mike Fitzpatrick wrote on Sep 01, 2016
The most likely cause is that you've defined an IRAFARCH environment variable set to 'linux64' instead of 'linux'. If you are indeed on a 64-bit machine then you should install the linux64 binaries, otherwise check to see whether your startup files are setting the wrong IRAFARCH.
ddayjuno wrote on Sep 01, 2016
Thanks for the reply.
How do I check what my IRAFARCH environment variable is set as? I can't seem to find it in my login.cl, and my uparm directory is just empty (haven't gotten iraf to run properly yet, so haven't customized the environment at all really). (Sorry if these are obvious questions - I'm a beginner at iraf.)
Mike Fitzpatrick wrote on Sep 01, 2016
Type "echo $IRAFARCH" to print any value that is already set, then look in your
$HOME/.login $HOME/.cshrc $HOME/.bashrc $HOME/.profile
files to see if it is set there. If not, then the 'cl' command may be deriving that your architecture *should* be set to linux64 and is constructing the path that way but you only have the linux binaries installed. In that case, you cat set IRAFARCH as
setenv IRAFARCH linux (for .login and .cshrc)
export IRAFARCH=linux (for .bashrc and .profile)
to force the path, or else reinstall IRAF with linux64 binaries.
ddayjuno wrote on Sep 01, 2016
Thank you! It worked after manually setting IRAFARCH as you described.
Last post on Sep 01, 2016