problems with the linker

jhernando · ‎07-26-2009

Hi:

I've just installed ifort 11.1 build 046 in a new box with fedora 11 and, after an installer complaint (unrecognized either the kernel -2.6.29.5-191.fc11.x86_64 - or glibc - 2.10.1-2.x86_64) I forced the installation and it finished successfully (or it seemed so). Then I put in my .tcshrc source /opt/intel/Compiler/11.1/046/bin/ifortvars.csh ia64 (unsuccessful) but it run OK wiith ia32; ifort -V gave me an answer.

Now my problem: I test compiled a program ifort -c pru.f and is OK but with ifort pru.f -o pru the linker complains
ld: /usr/lib/crt1.o: No such file: No such file or directory.
As crt1.o is in /usr/lib64 I made a symbolic link and the complaint then was about crti.o which again is in /usr/lib64. But when the last complaint was
ld: skipping incompatible /usr/lib64/libm.so when searching for -lm
ld: cannot find -lm
I gave up. I think that the problem is due to not accepting ia64 for running ifortvars.csh. What do you think?

Thanks for any help

Jorge Hernando

TimP · ‎07-26-2009

Yes, IA64 (Itanium) is a totally different instruction set and requires a g++ installation which you will find only on such a system. The Intel64 compiler corresponds with the x86_64 linux system. Needless to say, after other even worse starts, the term intel64 was chosen by apparent analogy to AMD64.
If you have installed the 32-bit i386/i586/i686 linux, you will not be able to use even Intel64 software development components.

jhernando · ‎07-27-2009

Quoting - tim18

Yes, IA64 (Itanium) is a totally different instruction set and requires a g++ installation which you will find only on such a system. The Intel64 compiler corresponds with the x86_64 linux system. Needless to say, after other even worse starts, the term intel64 was chosen by apparent analogy to AMD64.
If you have installed the 32-bit i386/i586/i686 linux, you will not be able to use even Intel64 software development components.

It worked! intel64 did all the magic! Thanks a lot, now I'll start with checking the output but the compilation was OK.

Jorge hernando