iraf.net

I installed the new OSX Mavericks on machine to test, and as far as I can tell there are no IRAF issues with this update. Two things to note however:

1) You will likely need to re-install XQuartz in order to get X tools working again
2) You will need to install the new XCode 5 release for compilation to work.

Using the Sep18 release of XCode 4 seemed to work for 64-bit compilation, however Xcode 5 is needed for 32-bit builds. These are just quick checks, if you find an issue with Mavericks please report it here.

I have been trying to install IRAF on Mavericks and I'm running into some trouble. I'm not sure if it's an issue related to Mavericks or not but I thought I'd post it here instead of making a new thread.

I installed the combo IRAF following these instructions,

http://www.iac.es/sieinvens/siepedia/pmwiki.php?n=HOWTOs.IrafMacOSX

When I try to start IRAF by typing 'cl' or 'ecl' in an xgterm window I get the following error,

ERROR: No /iraf/iraf//bin.macintel/ecl.e binary found

There were no errors during the installation process so I don't know what might be going wrong. Please note that I did install a new XQuartz and updated XCode

The message may indicate a path problem (e.g. an invalid $iraf) or a binary incompatibility. Verify that /iraf/iraf/bin.macintel/ecl.e does indeed exist, then try executing it directly to see if there is a host error message of some kind. I checked that the binary is in the distribution file. Note it could also be a permissions problem, e.g. the /iraf path isn't readable as you for some reason.

With v2.16.1 a root install is not required and you can do everything from your normal user account:

Thank you for replying to my question.

I checked the directories in my /iraf/iraf directory and I have a bin.macintel directory and a bin.macosx directory. ecl.e and cl.e do not exist in the bin.macintel directory but they are in bin.macosx. What would you recommend? Would it be okay to move the the files from bin.macosx to bin.macintel or should I change the the path to point to bin.macosx?

Also, does this indicate that something went wrong with my installation?

If you got the iraf-all.tar.gz, iraf-macosx.tar.gz or iraf.macx.x86_64.tar.gz files then there should definitely be a cl.e/ecl.e binary in the bin.macintel directory (along with other *.a and *.e files). If these are missing then there might have been a problem with the download (e.g. it was incomplete or corrupted somehow) or perhaps it was unpacked in a different location. The bin.macosx directory is for 32-bit binaries, these should work however if there was a download problem these may be incomplete in some other way.

Try downloading again using the previous instructions (i.e. with the 'ftp' command and not from a link in a web browser). The bin.macintel directory is normally what you should be using under Mavericks.

Okay, things seem to be working now. Thank you for your help.

I have Mavericks, IRAF installed via Ureka, Xcode fully updated and Xquartz. IRAF seems to be working ok but I can't get the external deimos package to work. It loads and I am able to pear the scripts, but when I try to execute dissimulator (I mean I enter the parameters and hit :go) I get
ERROR: Abnormal termination of child process '??'

I don't know where to start with debugging....

Thanks!

The DEIMOS package isn't one we distribute, was this part of Ureka or did you get it on your own? An 'abnormal termination' message usually means a binary incompatibility of some kind, e.g. the package binary is for/includes a PPC architecture or a shared library is not available. If this was included in your Ureka distro then you should followup with the Gemini/ST folks, if you got it on your own you should try recompiling on the new system.

Note that if you execute the demos package binary from the unix level you might get a more informative error message indicating what the problem is.

Fritz -
Thanks. I tried to recompile by going to the deimos package directory and run mkpkg, it seems to finish, but throws errors like
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/libtool: warning same member name (trace.o) in output file used for input files: trace.o and: /Users/gal/Work/iraf/deimos/src/libpkg.a(trace.o) due to use of basename, truncation and blank padding

I removed libpkg.a and the *.o files I could find, and recompiled again; this time it finished cleanly. I can epar the various scripts but when I try to execute I still get
ERROR: Abnormal termination of child process '??'

I then noticed that the mkpkg has a line
$move xx_deimos.e deimosbin$x_deimos.e
and that it was creating a file called deimosbinx_deimos.e in the src/ directory. So I renamed that file to x_deimos.e and put it in the proper bin directory. That finally worked!

Not sure why mkpkg doesn't know what is deimosbin$...but at least it works.

Thanks
Roy

Hello,

I recently installed iraf on Mavericks, and I get a complete crash of cl and xgterm when iraf attempts to open the plotter (for example, "implot test.fits". The error message is "Bus error."

I have tried the Ureka install as well as the manual /iraf/iraf/ install, and get the same error with both.

I have XCode 5 and the latest XQuartz (re-installed).

I realize that this is a very vague description of the problem, but I'm not sure what to do.

Thanks,

Jeremy

This hasn't been reported before, and I'm not sure whether the bus error is coming from the XGterm, the CL, or the IMPLOT task...or whether it might be related to your 'test.fits' file.

To sort it out, try starting up the xgterm window and then logging into iraf vi the 'cl' command as separate steps (as opposed to using the v2.16.1 'iraf' alias or an "xgterm -e cl" command), that way if the CL or task dies it won't cause the xgterm to go away. Then use a command like

cl\$this->_split2($m[0]) prow dev$pix 12

This will use the standard test image and if it works, try on your test.fits file to see if it then fails.

Lastly, since you installed several versions be sure that you're using the version you think you are, e.g. do

cl\$this->_split2($m[0]) show iraf

It's possible your .cshrc/.bashrc file might be redefining the iraf root/version when the 'cl' command is being executed. If things still fail, try doing

% ulimit -c unlimited (for default Bash shell)
or % limit coredumpsize unlimited (for C-shell)

before starting IRAF to see if you can get a core dump of whatever is crashing (it will be a 'core.XXXXX' filename), if you do then please upload it to the anonftp at ftp://iraf.noao.edu/pub so I can have a look.

Thank you for the very speedy reply!

Here is what I have done using the Ureka iraf install:

xgterm &
limit coredumpsize unlimited
cl
cl\$this->_split2($m[0]) prow dev$pix 12

At this point, the xgterm vanishes and no core file is generated. The original xterm where xgterm was spawned says:
[1] + Bus error xgterm

If I do mkiraf and choose xterm rather than xgterm and run your prow command, then the plotter works and cl does not crash!

Thanks,

Jeremy

Do the 'limit' command from the window that starts the xgterm BEFORE you start xgterm......

I uploaded the core: core.11667

Thanks, but it isn't showing anything useful yet. Could you also upload the xgterm binary you are using as well (e.g. do a "which xgterm" to find it).

Think I figured it out: Under the X11-\$this->_split2($m[0])Preferences-\$this->_split2($m[0])Output panel be sure the 'Colors' option is set to "From Display" and not something like '256 colors'. You'll need to re-launch X11 for the change to take effect, but with 256 as the setting I can reproduce the Bus Error.

That's it!!!

Thank you _very_ much for helping me get this working.

Best,

Jeremy

That's it!!!

Thank you _very_ much for helping me get this working.

Best,

Jeremy