Some experiments I've performed says
that "incompatible" -openmp -static options
for ifc 6.0 under RH 7.2 are mainly ifc problems
(because w/help of ifc 5.0 I can generate
I've prepared some executable modules for
standard linpack (n=1000) test. Source calls
some lapack routines which I use from Atlas 3.4.1
libraries or MKL libraries.
I work with academic versions of ifc 5.0 and 6.0.
Options used are -O3 -tpp6 -openmp
There is in particular 2 computers I use:
1)With RH 6.2, ifc 5.0 and MKL
2) With w/RH 7.2, ifc 6.0
and tuned ATLAS 3.4.1 generated for ifc 6.0.
If I understood Release Notes for ifc 6.0
correctly, it's impossible to use -openmp -static
combination of options (at least under RH 7.2,
where I tried to do this); the final executable
leads to segmentation fault.
But under ifc 5.0 w/RH 6.2 all works fine if
I use MKL libraries; by default it creates statically
linked executable module. The corresponding
executable runs on my RH 7.2 w/o problems.
OK, now I build static executable (using ld -static)
in RH 7.2: from partially linked executable module
created after translation and linking w/ifc-5.0
under RH 6.2 and
ATLAS-3.4.1 tuned libraries created by me w/ifc 6.0
under RH 7.2. The final module works OK.
Resume: it looks that it's ifc 6.0 problem, and
not RH 7.2 Linux error, because ifc 5.0 and ld
can produce working statically linked executable module.
Zelinsky Inst. of Organic Chemistry