Iraf 2.15 Linux 32bit install
morrisonss wrote on Jan 23, 2012
When I tried to install Iraf V2.15 Linux 32bit using the download from the http://iraf.noao.edu website the install script wanted the bin.linux to be bin.redhat, and the noao/bin.linux to be /noao/bin.redhat I went in to the files that were unpacked from the download and changed these to match what it wanted and was able to install it, but then when I tried to open iraf it tried to find the ecl file in the bin.linux file, so I changed it back, and it now appears to be working, but I wanted to know if you think doing this will cause any other issues down the road. I also wanted to let you all know so that the install script could be corrected.
Mike Fitzpatrick wrote on Jan 23, 2012
What distribution of linux? Specifically, what file did you download and install? Can you elaborate on "wanted bin.linux to be bin.redhat", was there a specific error message? Do you define a IRAFARCH environment variable from previous install that might be forcing the use of 'redhat'?
Otherwise, v2.15 will use either bin.linux or bin.redhat binaries interchangeably if needed. There may be issues with compiling local tasks/packages, but that would depend on the package and the answers to the above.
Otherwise, v2.15 will use either bin.linux or bin.redhat binaries interchangeably if needed. There may be issues with compiling local tasks/packages, but that would depend on the package and the answers to the above.
morrisonss wrote on Jan 23, 2012
I am using Fedora 14 32bit. I downloaded the IRAF V2.15 Release for Linux 32-bit (66MB) file from the site http://iraf.noao.edu homepage. As far as I could determine I don't have an IRAFARCH environment variable defined, though I did have a previous version of iraf that I removed. I got the errors shown below, but was able to get around them by changing the directory names from .linux to .redhat, though I had to change them back after install for the login.cl to find ecl.
Checking Core system binary directory ... [ FAIL ]
*** The core system binary directory, /iraf/iraf/bin.redhat, does
*** not appear to contain the proper binaries. The IB distribution
*** files should be unpacked in this directory.
Checking NOAO package binary directory ... [ FAIL ]
*** The NOAO package binary directory, /iraf/iraf/noao/bin.redhat, does
*** not appear to contain the proper files. The NB distribution
*** files should be unpacked in this directory.
Checking Core system binary directory ... [ FAIL ]
*** The core system binary directory, /iraf/iraf/bin.redhat, does
*** not appear to contain the proper binaries. The IB distribution
*** files should be unpacked in this directory.
Checking NOAO package binary directory ... [ FAIL ]
*** The NOAO package binary directory, /iraf/iraf/noao/bin.redhat, does
*** not appear to contain the proper files. The NB distribution
*** files should be unpacked in this directory.
Mike Fitzpatrick wrote on Jan 23, 2012
I think the problem is in how the iraf.lnux.x86.tar.gz file was built, i.e. it includes only the 'bin.linux' directories and not the 'bin.redhat' symlinks that point to bin.linux. The install script determines the platform architecture by looking for a /etc/redhat-release file (Fedora is a derivative of redhat), however the 'cl' command script uses the more generic output of 'uname' and so comes up with linux as the architecture. If the symlinks were present (as in the combined iraf-linux.tar.gz files) then this difference doesn't matter.
I'll fix the distribution for the next release, until then you can just do
ln -s bin.linux bin.redhat
in the $iraf and $iraf/noao directories.
I'll fix the distribution for the next release, until then you can just do
ln -s bin.linux bin.redhat
in the $iraf and $iraf/noao directories.
Last post on Jan 23, 2012