This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
RE: Linker Problem
- To: 'Alexandre Oliva' <aoliva at redhat dot com>
- Subject: RE: Linker Problem
- From: "DiFrango, Ron" <ron dot difrango at capitalone dot com>
- Date: Tue, 26 Jun 2001 16:53:14 -0400
- Cc: gcc-bugs at gcc dot gnu dot org
Alexandre,
What I have determined, is that the problem seems to be with the name
mangling. The functions that I am having trouble linking to are C++ name
mangled in a SunWorks Version 5 compiler.
I did an nm on the library I am linking (the one that contains the function
below) and here is the result:
__0FISU_LoginP6FAPI_tR6Mlogin_data_tP6Pemployee_data_t
which I think is equivalent to:
SU_LoginP6FAPI_tR6Mlogin_data_tP6Pemployee_data_t
So now the question is, can I some how tell the linker to map from the GCC
mangled name to the one that is actually in the library? Or is there some
other way to get around this issue?
Thank again!
Ron
-----Original Message-----
From: Alexandre Oliva [mailto:aoliva@redhat.com]
Sent: Tuesday, June 26, 2001 4:47 PM
To: DiFrango, Ron
Cc: gcc-bugs@gcc.gnu.org
Subject: Re: Linker Problem
On Jun 25, 2001, "DiFrango, Ron" <ron.difrango@capitalone.com> wrote:
> fatal: relocation error: file
> /export/home/u50596/beta/pdm_source/libUnivapi.so
> : symbol SU_Login__FP5API_tR12login_data_tP15employee_data_t:
> referenced symbol not found
So, in which library is this symbol defined?
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
**************************************************************************
The Information transmitted herewith is sensitive information intended only
for use to the individual or entity to which it is addressed. If the reader
of this message is not the intended recipient, you are hereby notified that
any review, retransmission, dissemination, distribution, copying or other
use of, or taking of any action in reliance upon, this information is
strictly prohibited. If you have received this communication in error,
please contact the sender and delete the material from your computer.