iraf.net

Hello,
I just installed the 2.13beta2 Red Hat linux (rhux) binaries on my PIII laptop running Debian Sarge (3.1) and it works great!
Many thanks to Mike and the other iraf developers.Here the installation instructions.
With respect to a normal iraf installation you need a few caveats:(1) first of all, install the "termcap-compat" package. From root:[code:1:b216f919c9]
# apt-get install termcap-compat
[/code:1:b216f919c9](2) when unpacking ib and nb binary packages, make sure to unpack them in /iraf/irafbin/bin.redhat and /iraf/irafbin/noao.bin.redhat, as if you were installing on a Red Hat system:[code:1:b216f919c9]
iraf% mkdir /iraf/irafbin/bin.redhat
iraf% cd /iraf/irafbin/bin.redhat
iraf% tar xfvz /path/to/ib.rhux.x86.gziraf% mkdir /iraf/irafbin/noao.bin.redhat
iraf% cd /iraf/irafbin/noao.bin.redhat
iraf% tar xfvz /path/to/nb.rhux.x86.gz
[/code:1:b216f919c9](3) edit and run the install script.
We are using Red Hat binaries, but install script will guess (from uname) a generic Linux system, and this will cause errors in the installation (i.e. the install will not find binaries in the bin.linux directories, because they are in bin.redhat directories).
The "-m redhat" option will tell install script to act as it was a Red Hat installation, but this will cause a "foreach: No match" error when checking file permissions. This is caused by a wrong value of $hmach variable: it should be "redhat" but is "linux".
So edit the following section of install script which process command line options:[code:1:b216f919c9]
case -m: # set machine type
if ("$2" != "") then
shift
else
ERRMSG "missing argument to '-m <mach>' switch"
exit 1
endif
set mach = "$1"
breaksw
[/code:1:b216f919c9]and change to:[code:1:b216f919c9]
case -m: # set machine type
if ("$2" != "") then
shift
else
ERRMSG "missing argument to '-m <mach>' switch"
exit 1
endif
set mach = "$1"
set hmach = "$1" # add this line to prevent foreach error
breaksw
[/code:1:b216f919c9]then you can run the install script and proceed with the normal iraf installation. Emiliano.

Hi Emiliano,Thanks for the post. The idea of a '-m' flag to the install script is interesting and probably something I'll include. I do have a few small comments however: The termcap-compat is now needed for the ECL but I've already modified the build so this isn't needed.More importantly, I presume you've defined an IRAFARCH in your environment as 'redhat'? This is why you're able to install in a bin.redhat directory but for users who don't define an environment things like the cl.csh check for the existance of a /etc/redhat-release file when determining the arch. On Debian this won't be found and the empty bin.linux will be used instead. For the final release I'd like to merge all the linux versions to avoid stuff like this. It is good to know that the current redhat binaries work under Debian Sarge, but a simpler install may be to simply install the IB/NB file under a 'bin.linux' directory and the for the HSI copy the iraf$unix/bin.redhat to iraf$unix/bin.linux (or make a symlink). The HSI bin contains the XC/MKPKG binaries but also has the hardcopy printer translators (which is why the install script is looking there when making links in the system). Anyway, thanks again for the input. BTW, I have recently built the system under Sarge and there weren't any problems or hiccups. Same goes for some other debian-based releases.Cheers,
-Mike

Hello Mike,
I forgot to define IRAFARCH :shock:
anyway, from the ecl:
[code:1:a392d28be1]
ecl> !echo $IRAFARCH && echo $IRAFBIN
redhat
/iraf/iraf/bin.redhat
[/code:1:a392d28be1]By the way: system commands like "!echo" are not stored in the ecl history; is it a bug or a feature?I did not make many tests up to now, only display of a few images and commands like imhist, pcol and so on... is there a testsuite (data + scripts) to download and run?Cheers,
Emiliano

[quote:cfde9614ba]
By the way: system commands like "!echo" are not stored in the ecl history; is it a bug or a feature? [/quote:cfde9614ba]It looks better if we just call it a feature 8-) I'll add it to the list since it is easy. Note that there are known limitations in the tab-completion as well which I also hope to address and are already on "the list".-Mike

Hello,Here is my 99 cents contribution. I just successfully instaled IRAF beta in linux gentoo using the redhat binaries (untared into *.linux) as suggested.
I wast getting the foreach: No match error while running the install script and the solution was to create a simlink in:/iraf/iraf/unix/from bin.linux to bin.redhat:cd /iraf/iraf/unix/
ln -s bin.redhat bin.linuxinstalled successfuly but...
=======
I also had to install the
libtermcap-compat librariesemerge -v libtermcap-compat===
cheers
It works!!!now external packages...

This page describes how to setup IRAF on a Ubuntu/Debian machine. Apart from the exact commands, there are some instructions in square brackets that need to be followed. Installation of X11IRAF, DS9, Tables, and STSDAS are included.http://geco.phys.columbia.edu/~rubab/iraf/