This is the mail archive of the
binutils@sources.redhat.com
mailing list for the binutils project.
Linking GCC obgject files with Intel FORTRAN for linux
- To: binutils at sources dot redhat dot com
- Subject: Linking GCC obgject files with Intel FORTRAN for linux
- From: "W Bauske" <wsb at paralleldata dot com>
- Date: Fri, 28 Sep 2001 19:09:25 -0500
- Organization: PDS Inc.
Hello,
Hopefully someone can help me understand what I've done wrong.
I have an application that uses C for the main program and calls
FORTRAN subroutines to do the real work. I had been using the
Intel FORTRAN Beta compiler without difficulty. Just had to add
the Intel libraries to the link libs when I linked. Now that Intel
have released the real compiler, the links fail with missing
symbols.
/z/home/intel.compilers/ifc.pro/compiler50/ia32/lib/libintrins.so: undefined reference to
`__gdt_lastone'
/z/home/intel.compilers/ifc.pro/compiler50/ia32/lib/libintrins.so: undefined reference to
`__gdt_firstone'
collect2: ld returned 1 exit status
I found a file in the Intel directories called icrt.link:
/* static char cvs_id[] = "$Id: icrt.link,v 1.1 2001/02/16 09:16:06 grigory Exp $"; */
/* for ICC C++ exception handling */
SECTIONS
{
.data1 :
{
*(.data1) /* Original .data1 section */
PROVIDE(__gdt_firstone = .); /* _GDT *__gdt_firstone */
*(.gdt)
*(.gnu.linkonce.g.\$gdt\$*)
PROVIDE(__gdt_lastone = .); /* _GDT *__gdt_lastone */
*(.edt)
*(.gnu.linkonce.e.\$edt\$*)
}
}
This appears to me to be some sort of linker directives where they provide
symbols for the front and back of the thing called a 'gdt'. If someone has
an idea about what Intel did and how to translate it to ld type info, please
let me know. Perhap a snippet of asm/directives could do the same thing?
Thanks,
Wes Bauske (please reply directly to me at wsb@paralleldata.com)