iraf.net

Following an unexpected upgrade to the operating system to RHEL4, IRAF
has stopped working for me. The person who installed IRAF originally
in May for me is unavailable. I've had a rummage around, but as an
inexperienced IRAF user, it's not clear what needs doing. Is it a
queston of updating $PATH, or invoking a script to create aliases?I did get our sys admin to restore the /iraf link. He created a root
password for my machine and gave it to me, so I was able to make the
links /usr/include/iraf.h and libncurses.so.4.RHEL 4 also reports the pty problem for which you have a new xgterm
for Fedora 2 and Mandrake 10. Will that also work for Redhat EL?I tried xiraf. DS9 and an xgterm appear briefly, but in the xgterm
xiraf barfs because the cl command isn't found. BTW I found a
couple of errors under the "Load the X-resources of XGterm" section
where the line
if ( -e \$X11IRAF_DIR/app-defaults/XGterm ) then
shouldn't escape the dollar. The END_ERROR_MESSAGE_4 has a double
negative. s/not located neither/located neither/.Thanks,Malcolm Currie

Hi Malcolm,
It sounds as if all you need to do is rerun the IRAF install
script to restore the IRAF commands (mkiraf, cl, etc). To do this,
become the root user, type 'csh' to begin a C-shell as root, and
then # setenv iraf /iraf/iraf/ <- trailing '/' required
# cd $iraf/unix/hlib <- go to hlib$ directory
# ./install -n <- do a no-op "install" to see what happens
# ./install <- do it for real w/out the -nOnce that's done the commands should be in the 'local bin directory',
which needs to be in your path. This should also fix the xiraf problem
but you'll need to contact the author about the rest. As far as we know
the pty-fixed xgterm works fine under RHEL and similar systems.
Hope this helps, let us know if you still have probelems or
questions.Cheers,
Mike Fitzpatrick

Mike,That's done the trick. If the commands were in /usr/local/bin before,
then it makes sense. cl and xiraf are working again. Many thanks.Now I can attempt to sort out why the cl is not finding the
isophote$x_isophote.e STSDAS executable, which is where I'd reached
before some major end-of-Starlink job came up.Malcolm

Following an unexpected upgrade to the operating system to RHEL4, IRAF
has stopped working for me. The person who installed IRAF originally
in May for me is unavailable. I've had a rummage around, but as an
inexperienced IRAF user, it's not clear what needs doing. Is it a
queston of updating $PATH, or invoking a script to create aliases?I did get our sys admin to restore the /iraf link. He created a root
password for my machine and gave it to me, so I was able to make the
links /usr/include/iraf.h and libncurses.so.4.RHEL 4 also reports the pty problem for which you have a new xgterm
for Fedora 2 and Mandrake 10. Will that also work for Redhat EL?I tried xiraf. DS9 and an xgterm appear briefly, but in the xgterm
xiraf barfs because the cl command isn't found. BTW I found a
couple of errors under the "Load the X-resources of XGterm" section
where the line
if ( -e \$X11IRAF_DIR/app-defaults/XGterm ) then
shouldn't escape the dollar. The END_ERROR_MESSAGE_4 has a double
negative. s/not located neither/located neither/.Thanks,Malcolm Currie

Hi Malcolm,
It sounds as if all you need to do is rerun the IRAF install
script to restore the IRAF commands (mkiraf, cl, etc). To do this,
become the root user, type 'csh' to begin a C-shell as root, and
then # setenv iraf /iraf/iraf/ <- trailing '/' required
# cd $iraf/unix/hlib <- go to hlib$ directory
# ./install -n <- do a no-op "install" to see what happens
# ./install <- do it for real w/out the -nOnce that's done the commands should be in the 'local bin directory',
which needs to be in your path. This should also fix the xiraf problem
but you'll need to contact the author about the rest. As far as we know
the pty-fixed xgterm works fine under RHEL and similar systems.
Hope this helps, let us know if you still have probelems or
questions.Cheers,
Mike Fitzpatrick

Mike,That's done the trick. If the commands were in /usr/local/bin before,
then it makes sense. cl and xiraf are working again. Many thanks.Now I can attempt to sort out why the cl is not finding the
isophote$x_isophote.e STSDAS executable, which is where I'd reached
before some major end-of-Starlink job came up.Malcolm