Posted: Sun Oct 29, 2006 11:53 pm Post subject: x86.64 iraf
I am running iraf on linux on the 64-bit x86 (AMD64) platform. Everything seems to work fine, except when I try to use "fc" to compile a IRAF/Fortran program.
It gives a large number of warnings all like:
/usr/bin/ld: warning: i386 architecture of input file `/iraf/iraf/unix/bin.redhat/libcompat.a(C_name.o)' is incompatible with i386:x86-64 output
I get basically one line like this one for every library in /iraf/iraf/unix/bin.redhat/
Then it creates a binary but it does not run. That is, it runs but returns the prompt without doing anything.
Is there full support for this platform? What should I do?
Compilation is not supported on 64-bit systems however the 32-bit binaries are known to work. What this means is that you'll need to compile your programs on a 32-bit system and move them over when done. Full support for 64-bit systems is on the list of projects but is a fairly big effort due to the amount of testing required even beyond the basic port.
The error means the binary is trying to load the libg2c shared library and finding only a 64-bit version. There may be some sort of "32-bit compatability" package you can install on your machine to workaround this, otherwise you're best bet is to find a statically linked binary for the package. I may be able to build one later today if you don't have any luck.
This was built from the latest RVSAO 2.5.3 sources from ftp://cfa-fta.harvard.edu/pub/iraf/rvsao-2.5.3.tar.gz. Just download the file and rename it 'x_rvsao.e' and put it in your package bin directory. If you still get the segvio then you should contact the package author (Doug Mink reads this site occassionally and may notice this message). Hope it helps.
I rebuilt the static binary at http://iraf.net/pub/fitz/x_rvsao.e-LINUX_STATIC from the latest RVSAO 2.7.8 sources so I'd suggest you download this and install it in the RVSAO bin.redhat directory. The linux scisoft distribution may also be a little old for your OS and you'll see similar problems with other binaries, chances are good that simply relinking the package on your machine will use the newer libs on your machine and likewise solve the problem.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum