Re: Difference in mangling
From: Lew Pitcher (Lew.Pitcher_at_td.com)
Date: 07/29/03
- Next message: Lew Pitcher: "Re: Difference in mangling"
- Previous message: lomat: "Difference in mangling"
- In reply to: lomat: "Difference in mangling"
- Next in thread: Lew Pitcher: "Re: Difference in mangling"
- Reply: Lew Pitcher: "Re: Difference in mangling"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 29 Jul 2003 10:39:12 -0400
lomat wrote:
> Hello,
>
> I am using VisiBroker 4.0 on RedHat 8.0 with GCC 3.2.
>
> When I do a "nm liborb_r.so | grep _invoke", I get some output. The symbol
> of my intrest is manged as below,
> 002f6270 T _preinvoke__12CORBA_ObjectPCc
>
> Now when I build an app that links to liborb_r.so, and uses the _preinvoke
> API, GCC mangles this symbol as follows,
> U _ZN12CORBA_Object10_preinvokeEPKc
>
> In short, (as mangling is compiler dependent) my compiler is mangling the
> symbols in a way different from the compiler that was used to build the
> library I am trying to link to. As a result I am getting an un-resolved
> symbol error. How do I solve this?
IIRC, GCC 3 changed a number of C++ related things, including how it mangled
the names. Likely, liborb_r.so was compiled with GCC 2, so falling your
compiler back to GCC 2 might fix your mangling problem.
-- Lew Pitcher, IT Consultant, Application Architecture Enterprise Technology Solutions, TD Bank Financial Group (Opinions expressed here are my own, not my employer's)
- Next message: Lew Pitcher: "Re: Difference in mangling"
- Previous message: lomat: "Difference in mangling"
- In reply to: lomat: "Difference in mangling"
- Next in thread: Lew Pitcher: "Re: Difference in mangling"
- Reply: Lew Pitcher: "Re: Difference in mangling"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|