Problems with 64-bit Fedora SPP
Doug Mink wrote on Nov 30, 2007
I just got a new computer today, a dual processor, dual core Sun machine running 64-bin Fedora Linux. When I try compiling one of my SPP packages on it, the files complie OK, but I get lots and lots of messages like this when linking:
/usr/bin/ld: warning: i386 architecture of input file '/data/oir/IRAF2.13//iraf.pkg/noao/bin.redhat/libsmw.a(shdr.o)' is incompatible with i386:x86-64 output
Is there something I can set? Or do I need a whole new set of IRAF binaries? The old executables worked fine, but I need to fix some bugs/add some features.
-Doug Mink
/usr/bin/ld: warning: i386 architecture of input file '/data/oir/IRAF2.13//iraf.pkg/noao/bin.redhat/libsmw.a(shdr.o)' is incompatible with i386:x86-64 output
Is there something I can set? Or do I need a whole new set of IRAF binaries? The old executables worked fine, but I need to fix some bugs/add some features.
-Doug Mink
Mike Fitzpatrick wrote on Nov 30, 2007
Compilation on 64-bit systems is not yet supported, you'll have to use pre-built 32-bit binaries for both the core system and external packages.
With proper compatability libraries installed on your machine and much munging of compile time flags to add a '-m32' option, it is sometimes possibles to build 32-bit binaries on a 64-bit machine but this is not something for mere muggles to attempt.
-Mike
With proper compatability libraries installed on your machine and much munging of compile time flags to add a '-m32' option, it is sometimes possibles to build 32-bit binaries on a 64-bit machine but this is not something for mere muggles to attempt.
-Mike
Doug Mink wrote on Nov 30, 2007
fitz
With proper compatability libraries installed on your machine and much munging of compile time flags to add a '-m32' option, it is sometimes possibles to build 32-bit binaries on a 64-bit machine but this is not something for mere muggles to attempt.
Then I guess I'll just have to see whether I'm still an IRAF wizard.
-Doug
nelly wrote on Nov 30, 2007
Hi, I am a new iraf user, using a new DELL 64-bit computer , and running iraf-2.12.2 which is installed on the department server. everything works so far, expect when I compile routines using 'fc' I have compilation errors, similar to the ones that Doug has reported. (at the end the file gets compiled, but when I run it , i get the message 'segmentation fault'.)
This is the error message:
'/usr/bin/ld: warning: i386 architecture of input file `/iraf/iraf/unix/bin.redhat/libos.a(zraloc.o)' is incompatible with i386:x86-64 output '
I don't really understand Mike's answer about adding a -m32 option. Can anyone please help explain more in details, what can be done? or does anyone have some new clues about what to be done???
Thank you!
Nelly
This is the error message:
'/usr/bin/ld: warning: i386 architecture of input file `/iraf/iraf/unix/bin.redhat/libos.a(zraloc.o)' is incompatible with i386:x86-64 output '
I don't really understand Mike's answer about adding a -m32 option. Can anyone please help explain more in details, what can be done? or does anyone have some new clues about what to be done???
Thank you!
Nelly
Mike Fitzpatrick wrote on Nov 30, 2007
For compilation using 'fc', you would do something like:
where the '/' is used to passthru the -m32 flag to the underlying compilers. The earlier comments about this being non-trivial referred mostly to the need to install 32-bit GCC libraries alongside the default 64-bit compiler. Depending on what you're building there may be other dependencies as well, but try the above first and hope for the best.
-Mike
cl> fc -/m32 mytask.fwhere the '/' is used to passthru the -m32 flag to the underlying compilers. The earlier comments about this being non-trivial referred mostly to the need to install 32-bit GCC libraries alongside the default 64-bit compiler. Depending on what you're building there may be other dependencies as well, but try the above first and hope for the best.
-Mike
nelly wrote on Nov 30, 2007
Thanks Mike for your reply!!
this works, problem solved!
in fact it seems to work without the '/' as well!
Nelly
this works, problem solved!
in fact it seems to work without the '/' as well!
Nelly
Last post on Nov 30, 2007