ifort 11.1. seg faulting with no options

[markreynolds1234]

Hi,

I have a newly install 64 bit Red Hat Linux based server with ifort 11.1. Running the ifort binary with no options at all gives a segmentation fault. (See output from strace)

....
futex(0x35fb6030ec, FUTEX_WAKE_PRIVATE, 2147483647) = 0
open("/state/partition1/apps/intel/Compiler/11.1/073/bin/intel64/../../lib/intel64/ifort_libFNP.so", O_RDONLY) = 3
read(3, "\\177ELF\\2\\1\\1\\0\\0\\0\\0\\0\\0\\0\\0\\0\\3\\0>\\0\\1\\0\\0\\0\\320/\\23\\0\\0\\0\\0\\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=7640928, ...}) = 0
mmap(NULL, 8854512, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x2b286e4a3000
mprotect(0x2b286eb63000, 1044480, PROT_NONE) = 0
mmap(0x2b286ec62000, 552960, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6bf000) = 0x2b286ec62000
mmap(0x2b286ece9000, 179184, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2b286ece9000
close(3) = 0
futex(0x2b286ed02128, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x2b286ed12400, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x2b286ed149e0, FUTEX_WAKE_PRIVATE, 2147483647) = 0
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++

The server is running 2.6.18-164.6.1.el5. I'm a little confused as I'm not even trying to compile anything and its failing.

Any thoughts appreciated,

Mark

[Ron_Green]

If it's RHEL 6, 11.1 is currently not supported under this new OS release. See the ReleaseNotes document for support versions of RHEL for your compiler version.

I do have this writeup for the 12.0 ( aka Composer XE 2011 ) compiler, and it may work for 11.1:

http://software.intel.com/en-us/articles/using-intel-compilers-for-linux-under-redhat-enterprise-linux/

You may wish to try 12.0. However, you may want to wait a few days - we have an update release for the compiler due to be posted any day now.

ron

[markreynolds1234]

Hi,

I tracked the problem down to a library issue in ldconfig. Ifort was linking against the wrong libraries. Its now running. Many thanks for you response.

Regards

Mark