iraf.net

After getting a new hard drive and upgrading to 10.8 I tried to reinstall IRAF using the same method I used previously. This time around the installation didn't want to work. Below is the output I got when I tried to install. I tried setting the 'Local unix commands directory' to /usr/bin and /usr/local/bin and both give the same error. Any ideas would be greatly appreciated.------------------------------------------------------------------------------------- IRAF V2.14 System Installation
================================ Welcome to the IRAF installation script. This script will first
prompt you for several needed path names. The system will be verified
for proper structure before the actual install begins, all error must
must be corrected before you will be allowed to continue. Recommend-
ations for fixing problems will be made but no corrective action will
be taken directly. Once properly installed, you will be allowed to
do some minimal configuration. For each prompt: hit <CR> to accept the default value, 'q' to quit,
or 'help' or '?' to print an explanation of the prompt.
========================================================================
===================== Query for System Settings ======================
========================================================================New iraf root directory (/iraf/iraf):
Default root image storage directory (/iraf/imdirs):
Local unix commands directory (/usr/local/bin): /usr/bin========================================================================
===================== Verifying System Settings ======================
========================================================================Hostname = nicholas-meek-1.umer OS version = Darwin 11.4.2
Architecture = macosx HSI arch = macosx
New iraf root = /iraf/iraf Old iraf root = /iraf/iraf
New imdir = /iraf/imdirs Old imdir = /iraf/imdirs
Local bin dir = /usr/bin
Checking definition of iraf root directory ... [ OK ]
Checking iraf root and imdir directory ... [ OK ]
Checking iraf directory write permissions ... [ OK ]
Checking file permissions ... [ OK ]
Checking proper iraf tree structure in /iraf ...
Checking for 'iraf' subdir ... [ OK ]
Checking for 'irafbin' subdir ... [ OK ]
Checking for 'irafbin/bin.macosx' subdir ... [ FAIL ]
Checking for 'irafbin/noao.bin.macosx' subdir ... [ FAIL ] *** An error was detected in the structure of the iraf tree.
*** Your directory tree should look something like:
***
*** /iraf
*** / \
*** (AS) /iraf /irafbin
*** / \
*** (I bin.macosx noao.bin.macosx (N
***
*** The AS, IB, and NB distribution files are shown where they
*** should be unpacked. Please verify the structure and the
*** system architecture.Checking Core system binary directory ... [ FAIL ] *** The core system binary directory, /iraf/irafbin/bin.macosx, 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/irafbin/noao.bin.macosx, does
*** not appear to contain the proper files. The NB distribution
*** files should be unpacked in this directory.Checking that local bin directory exists ... [ OK ]
======================================================================
| An error occured during verification. Please take corrective |
| action before rerunning the install script. |
======================================================================

The first thing I would recommend is that you use the latest v2.16 system instead of the much older v2.14 release.The error messages mean that the install script is trying to setup your system for a 'macosx' architecture but isn't finding the binaries (probably because you have the 'macintel' binaries instead. You can define an IRAFARCH variable to override this in the install script, e.g.[code:1:e3d9271e16]reset IRAFARCH = macintel[/code:1:e3d9271e16]This is the first I've heard of somebody trying to use v2.14 on a 10.8 system (one way or the other) so there may be issues with 10.8 not supporting the PPC architecture any longer and so not recognizing the binaries.