Hi Carsten,
On Fri, May 16, 2008 at 12:33 AM, Carsten Neumann
<[EMAIL PROTECTED]> wrote:
> Ákos Balázs wrote:
>>> if you used the make/configure build you can see the configure line near
>>> the top of config.status
>>
>> That's handy to know. :-) In this case:
>>
>> ./configure --prefix=/usr/local --with-glut --enable-png
>> --enable-jpg --enable-gif --enable-mng --enable-tif
>> --with-qt=/usr/share/qt3 --enable-opt_drawtree
> hm, indeed nothing out of the ordinary...
That's what I thought aswell...
>> I'm fairly sure I have only this c++ compiler installed. I also have
>> gcc-2.95 for kernel stuff, but I don't think it matters. Maybe it's
>> the old compiler, but I'd prefer not having to install a newer one if
>> possible...
> ok, it was just a thought.
Maybe I'll try installing g++ 4.x tonight, if noone else has any idea... :/
>>> Can you try using objdump and grep to see if the symbols are present in
>>> any of the .o files ?
>>
>> Do you mean like this:
>>
>> $ objdump -x BaseLib/lib-opt/libOSGBase.so |grep
>> _ZN3osg6SFieldINS_6Color3IfEELi0EE14pushValueByStrEPKc
>> 00164ba0 w F .text 00000191
>> _ZN3osg6SFieldINS_6Color3IfEELi0EE14pushValueByStrEPKc
>>
>> so it seems to be in the BaseLib.
> hm, ok. Having reread the error message a couple of times now, I think
> this is related to how the linker handles templates. If a template is
> instantiated in multiple translation units with the same template
> arguments and these are later linked together the linker basically has
> to discard all but one of the identical instantiations.
> The message seems to suggest that it does not get this quite right, but
> other than looking through the compiler/linker options for a knob that
> can influence this I don't really know what to do now.
This would indicate a too old compiler, which would be bad news for me
but a sensible explanation nonetheless. However, what I don't get is
why only this symbol? I don't have the full buildlog at hand right
now, but I'm fairly sure the only problem was caused by this symbol.
Since OpenSG uses templates all over the place, I would expect many
symbols not being defined/discarded correctly.
> Has anybody else encountered something similar and remembers how to
> overcome this ?
I'd be most interested to know if this can be overcome at all.
Thanks,
Akos
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Opensg-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensg-users