This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
linking with vendor provided object files
- To: gcc-help at gnu dot org
- Subject: linking with vendor provided object files
- From: haithcoc at gdls dot com
- Date: Tue, 23 Oct 2001 15:03:58 -0400
- Cc: gcc-help at gcc dot gnu dot org;gcc;;
I am attempting to switch to the g++ compiler from the native SGI (IRIX)
compiler.
We use n32 abi, mips 4.
I use g++ to compile, ar to archive, and g++ to link.
My link command is as follows:
g++ -g -Lang:std -L<libpath1> ... -L<libpathn> -l<lib> ...-l<libn> -o
<exec_filename>
The problem that I am having is that some of the libraries are from outside
sources (performer, etc), and the name mangling is not the same as the
native compiler, so it is not finding a match. It results in "ld32: ERROR:
33: Unresolved text symbol".
I can link fine on the native compiler.
Compiling all of my libraries seemed to go fine - no warnings or errors,
but I can not rebuild the other libraries with gcc, and thus cannot link.
The mangled names for the same method are different from the native
compiler and gcc (I ran c++filt). Is there anyway to resolve the mangled
name differences problem?
Thanks in advance for any help,
Stephen