iraf.net

I upgraded one of my Macs to Lion yesterday, and cannot get IRAF to run, despite having done a complete reinstall of IRAF V2.15.1a. I tried the mac OSX 64-bit distribution and received the error message saying that "Power PC applications are not supported" Next I thought I would try the mac OSX 32 bit distribution. But, the instal failed with the following messages: Checking iraf directory write permissions ... [ OK ]
Checking Core system binary directory ... [ FAIL ] *** The core system binary directory, /iraf/iraf/bin.macintel, 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.macintel, does
*** not appear to contain the proper files. The NB distribution
*** files should be unpacked in this directory.

Hi Phil,I think this is just some architecture confusion (although I'll admit to not having tried Lion yet).The 32-bit 'macosx' arch is a universal binary, and while you can use a tool like "Monolingual" (Google it) to strip PPC from binaries, my understanding is that Universal bins should be fine. The 'macintel' 64-bit arch is pure Intel and unless they've changed the architecture code it should also work.Your install output appears to be looking for macintel, but if you're using the macosx binaries then it would explain the errors. You can always just install the iraf-macosx.tar.gz file that contains both sets of binaries, but keep in mind you can also set the IRAFARCH variable to force a particular architecture even if the default is something else. On many systems, Snow Leopard doesn't use 64-bit as the default boot kernel so a "uname -m" returns "i386" and IRAF tries to use the 'macosx' binaries unless IRAFARCH is set to override it.Lastly, you can always try running something like bin$x_images.e directly from the commandline to see whether the binary will actually run. You should see a ">" prompt (type 'bye' to quit) or else post back with the error message.[/quote]

1) Well, the version of IRAF I had installed before the update (universal binary) SHOULD have worked too, but something in Lion is failing to recognize that it's intel. I got the PPC message with a fresh (fresh!) install of the 64-bit.2) I think there is may be something missing/wrong with the version of the 32-bit distribution i downloaded, or its install script. I had
done a cd /iraf/iraf and then a sudo rm *
I then downloaded ftp://iraf.noao.edu/iraf/v215/PCIX/iraf.macx.uni.tar.gz
de-tared it, and ran the install script, with the errors you saw.I'll keep messing with it.

[quote:05629b7a49]1) Well, the version of IRAF I had installed before the update (universal binary) SHOULD have worked too, but something in Lion is failing to recognize that it's intel. I got the PPC message with a fresh (fresh!) install of the 64-bit. [/quote:05629b7a49]What happens when you type: % file /iraf/iraf/bin.macintel/x_system.e
% file /iraf/iraf/bin.macosx/x_system.eDoes it think they're both PPC/universal binaries?[quote:05629b7a49]
2) I think there is may be something missing/wrong with the version of the 32-bit distribution i downloaded, or its install script. I had
done a cd /iraf/iraf and then a sudo rm *
I then downloaded ftp://iraf.noao.edu/iraf/v215/PCIX/iraf.macx.uni.tar.gz
de-tared it, and ran the install script, with the errors you saw. [/quote:05629b7a49]In that case, do you have IRAFARCH set to 'macintel' or is it undefined?

Mike---
I'm getting myself more and more confused. Tonight I decided to go ahead and upgrade my SNOW LEOPARD MacBook Pro to 64-bit V15. Here's exactly what I did:sudo mkdir /iraf
cd /iraf
sudo mkdir iraf
sudo chmod a+w iraf
setenv iraf /iraf/iraf/
[moved iraf.maxs.x86_64.tar to /iraf/iraf/ and un-tared it]
sudo $iraf/unix/hlib/installThen:New iraf root directory (/iraf/iraf):
Default root image storage directory (/iraf/imdirs):
Local unix commands directory (/usr/local/bin): ========================================================================
===================== Verifying System Settings ======================
========================================================================Hostname = tig.local OS version = Darwin 10.8.0
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/local/bin
Checking definition of iraf root directory ... [ OK ]
Checking iraf root and imdir directory ... [ OK ]
Checking iraf directory write permissions ... [ OK ]
Checking Core system binary directory ... [ FAIL ] *** The core system binary directory, /iraf/iraf/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/iraf/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. |
======================================================================Okay. So, I checked:
printenv IRAFARCH returns macinteland of course (not really relevant since it is snow leopard but just for fun):
file /iraf/iraf/bin.macosx/x_system.e
/iraf/iraf/bin.macosx/x_system.e: cannot open `/iraf/iraf/bin.macosx/x_system.e'
and
file /iraf/iraf/bin.macintel/x_system.e
/iraf/iraf/bin.macintel/x_system.e: Mach-O 64-bit executable x86_64So, let me get THIS straight before I move onto Lion. In the interests of full discllosure I'm doing these sudo's as me, not as user "iraf" but that seems consistent with the release notes. What have I screwed up?thanks!
---phil

Phil,Contrary to what I was almost certain of, it appears the install script is one case where the IRAFARCH won't override the built-in architecture detection. I'll fix it for the next release.As for workarounds: Boot the machine to use the 64-bit OSX kernel by holding down the '6' and '4' keys after turning on the power. A "uname -m" should say x86_64 if you're in 64-bit mode, and the install script should then try to install the macintel arch. If you still see 'i386' then the system is using the 32-bit kernel. (Note, you can use 32-bit OSX and still run 64-bit application binaries). Once the system is installed, IRAFARCH=macintel will force the arch when you type 'cl'.

Phil,Contrary to what I was almost certain of, it appears the install script is one case where the IRAFARCH won't override the built-in architecture detection. I'll fix it for the next release.As for workarounds: Boot the machine to use the 64-bit OSX kernel by holding down the '6' and '4' keys after turning on the power. A "uname -m" should say x86_64 if you're in 64-bit mode, and the install script should then try to install the macintel arch. If you still see 'i386' then the system is using the 32-bit kernel. (Note, you can use 32-bit OSX and still run 64-bit application binaries). Once the system is installed, IRAFARCH=macintel will force the arch when you type 'cl'.

Phil,Contrary to what I was almost certain of, it appears the install script is one case where the IRAFARCH won't override the built-in architecture detection. I'll fix it for the next release.As for workarounds: Boot the machine to use the 64-bit OSX kernel by holding down the '6' and '4' keys after turning on the power. A "uname -m" should say x86_64 if you're in 64-bit mode, and the install script should then try to install the macintel arch. If you still see 'i386' then the system is using the 32-bit kernel. (Note, you can use 32-bit OSX and still run 64-bit application binaries). Once the system is installed, IRAFARCH=macintel will force the arch when you type 'cl'.

Hi, Mike---Okay, that solved my problem with install 64-bit IRAF on my snow leopard machine, and I think it points the way to what is going wrong on Lion.
I rebooted the machine into 64-bit OSX as you said, confirmed it with uname -m, and then explictly set IRAFARCH to macintel. I ran the install script and it worked fine, and cl came up fine. I did find, however, that when I rebooted back into 32-bit mode that cl would fail unless I explicitly set IRAFARCH to macintel. (It came up undefined.) If I did that, then everything works.So, I will tackle Lion next. THANKS!!!

Okay, 64-bit V15.1a is working fine under Lion. Lion comes up naturally as 64 bits, which is why the install worked earlier. I don't know why I was getting the PPC messages, but now it's fine. Well, at least implot dev$pix.imh does what you would expect. Might want to emphasize the importance in the release notes of explictly setting IRAFARCH. When it's undefined, my impression is that bad things happen.