Intel® C++ Compiler
Community support and assistance for creating C++ code that runs on platforms based on Intel® processors.
7956 Discussions

crt1.o file not recognized on OpenSUSE 10.3

heiga
Beginner
432 Views
Hi,

I tried to run configure script to compile my own program using intel C compiler. I received the following error message:

configure:2217: checking for C compiler default output file name
configure:2244: /rmt/intel/cc/11.0.083_64/bin/intel64/icc -g -lsvml -L/rmt/intel/fc/11.0.083_64/lib/intel64 -L/usr/lib64/gcc/x86_64-suse-linux/4.2.1 -lgfortran -lifcore conftest.c >&5
/usr/lib64/gcc/x86_64-suse-linux/4.2.1/../../../../lib64/crt1.o: file not recognized: File format not recognized

I'm using OpenSUSE 10.3, icc/ifort 11.0.083 (64-bit), binutils-2.17.50.20070726-14


I seached web and past forum discussions but I couldn't find any solution.
Does anyone have an idea to solve this problem?
0 Kudos
1 Reply
TimP
Honored Contributor III
432 Views
Quoting - heiga
Hi,

I tried to run configure script to compile my own program using intel C compiler. I received the following error message:

configure:2217: checking for C compiler default output file name
configure:2244: /rmt/intel/cc/11.0.083_64/bin/intel64/icc -g -lsvml -L/rmt/intel/fc/11.0.083_64/lib/intel64 -L/usr/lib64/gcc/x86_64-suse-linux/4.2.1 -lgfortran -lifcore conftest.c >&5
/usr/lib64/gcc/x86_64-suse-linux/4.2.1/../../../../lib64/crt1.o: file not recognized: File format not recognized

I'm using OpenSUSE 10.3, icc/ifort 11.0.083 (64-bit), binutils-2.17.50.20070726-14


If you're asking us to rank the problems here, starting with the worst, here's my stab:
1. -lgfortran will certainly break it, as ifort and gfortran run-time libraries are incompatible.
2. The normal way to use Intel compilers is to set PATH and LD_LIBRARY_PATH in the expected way, rather than attempt to set specific paths. Tools invoked by icc won't inherit the path of the icc which started them.
3. If you need -lsvml you have another problem somewhere. icc should include it by default in its generation of a linker script.
4. I'd have to look at how working build systems do their mixed Fortran/C configure tests. It seems more normal to make a C object and use Fortran to link, for a case with both Fortran and C. You appear to have only C, so it doesn't make sense to link any fortran libraries.
4. The default opensuse 10.3 binutils may not be sufficient if you set SSE4 options.

Surely some of these points are supported in past discussions.
0 Kudos
Reply