Re: Linking GCC compiled shared library using SunStudio
- From: James Kanze <james.kanze@xxxxxxxxx>
- Date: Tue, 4 Nov 2008 01:35:10 -0800 (PST)
On Nov 3, 2:08 pm, Doug McIntyre <mer...@xxxxxxxxx> wrote:
"adisa...@xxxxxxxxx" <adisa...@xxxxxxxxx> writes:
I have big problem,
I have just compiled my libraries with g++ 3.4 and it works well, but
I need to plugin that libraries inside Sun studio compiled
application.
Now I can NOT use the Sun workshop to compile my shared libraries
becasue there is an official bug and it did not compile it.
So please do you know if there is just a way to link the g++ shared
libraries in Sun studio application ?
There's no way to have portable C++ libraries because every
compiler mangles the symbols differently.
That's not really the issue. The reason here is that Sun CC and
g++ lay out classes (vtable, etc.) differently. All the name
mangling means is that you get the error at link time, rather
than a mysterious crash at runtime.
--
James Kanze (GABI Software) email:james.kanze@xxxxxxxxx
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34
.
- References:
- Linking GCC compiled shared library using SunStudio
- From: adisabat@xxxxxxxxx
- Re: Linking GCC compiled shared library using SunStudio
- From: Doug McIntyre
- Linking GCC compiled shared library using SunStudio
- Prev by Date: Re: Google groups troubles [was: Re: dh, the daemon helper]
- Next by Date: Re: portability: static vs. shared?
- Previous by thread: Re: Linking GCC compiled shared library using SunStudio
- Next by thread: Re: How to map a UNIX locale to SAS locale?
- Index(es):
Relevant Pages
|
