View on GitHub

IRAF Community Distribution

IRAF maintained by the community

Home | Installation | Packages | X11IRAF | PyRAF | Forum

IRAF 2.15 on a Powermac G5, 10.5 fails

fjjames wrote on Dec 31, 2010

I am trying to install IRAF 2.15 on a Power Mac, system 10.4. This is a new installation.
I downloaded the Mac OSX 32-bit (131MB) file, made the /iraf/iraf directories, and unpacked there. I then ran the install program, changed to my home directory, and ran mkiraf and cl.
I go the following:

indium:~ fjames$ cl
csh: setenv: Too many arguments.
dyld: Symbol not found: ___stack_chk_guard
Referenced from: /iraf/iraf/bin.macosx/ecl.e
Expected in: /usr/lib/libSystem.B.dylib

Trace/BPT trap

It seems that on this system, uname -m gives
indium:~ fjames$ uname -m
Power Macintosh

and so the irafarch.csh script breaks.

I modified that with
< setenv UNAME_M `$uname_cmd -m | tr '[A-Z]' '[a-z]' | tr ' ' '_'`
---
> setenv UNAME_M `$uname_cmd -m | tr '[A-Z]' '[a-z]'`
144c144
< else if ($MNAME_M == "x86" || $MNAME_M == "i386" || $MNAME_M == "ppc" || $MNAME_M == "power_macintosh") then
---
> else if ($MNAME_M == "x86" || $MNAME_M == "i386" || $MNAME_M == "ppc") then

and now irafarch.csh returns macosx, but running after running mkiraf
gives

dyld: Symbol not found: ___stack_chk_guard
Referenced from: /iraf/iraf/bin.macosx/ecl.e
Expected in: /usr/lib/libSystem.B.dylib

Trace/BPT trap

The configure script in the extern directory also does now work properly.
What have I missed?

Mike Fitzpatrick wrote on Dec 31, 2010

There is an incompatability in the libSystem used by 10.4 and the system used to build the ecl.e binary that causes the error. Since there is nothing substantially new in the ECL itself, using the older binary will work in almost all cases. If you haven't still got this around, I've put one at

ftp://iraf.noao.edu/iraf/v215/support/ecl.e.v214_macosx

Just download, make executable, and put in your iraf$bin.macosx directory. Starting IRAF as "cl -old" to run the old CL should also work.

The change to the irafarch.csh was made earlier in response to a local user's problem, but in general there's only limited support we can offer for 10.4 PPC systems due to a lack of hardware.

Last post on Dec 31, 2010