Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29281 Discussions

ifort on Precision Workstation running Red Hat

Anonymous22
Beginner
699 Views

I'm running into this error when I compile:

ld: skipping incompatible ---fill in the library--- when searching for ---said library---

ld: cannot find ---said library---

At first I was running in elf_i386 mode and the incompatible file was /usr/lib/libm.a, but after switching to elf_x86_64 (using -Wl,-elf_x86_64) the error that stopped the compile was an incompatible /opt/intel/fc/10.0.023/lib/libifport.a

Does incompatible refer to the change from a 32 bit to a 64 bit system? I'm running the later; shouldn't ifort be compatible?

0 Kudos
3 Replies
Anonymous22
Beginner
699 Views

Update: I added the command "-fpscomp nolibs" and now get the same error but for lifcore. It looks like elf_x86_64 is the wrong mode to run in.

I should here include that the mode i386linux returns a different error:

ld: unrecognized option --eh-frame-hdr

That option is not in my makefile; couldit be a compiler-given command? Any idea how to deal with that?

0 Kudos
TimP
Honored Contributor III
699 Views
If you have installed correctly, you choose 32- or 64-bit compilation and run-time libraries by running the corresponding environment variable script, in the /fc/ directory for 32- or /fce/ for 64-bit. You can't mix the options, paths, or libraries between 32- and 64-bit builds. If you are building with specific 32-bit libraries in your command, you will have to fix it to go to 64-bit mode. You seem to be expecting a lot of clairvoyance.
0 Kudos
Anonymous22
Beginner
699 Views
Not clairvoyance: basics. I was running fc on a 64-bit. Thank you for illuminating my error.
0 Kudos
Reply