Angelo Graziosi wrote:
> To test this new version of the compiler I have rebuild ROOT [1]. It
> builds fine, but when I try to build its tests, at least one fails in
> linking:
> d000037.o:(.idata$5+0x0): multiple definition of `__imp___ZTISt9exception'
> /usr/lib/gcc/i686-pc-cygwin/4.3.2/libstdc++.dll.a(d002074.o):(.idata$5+0x0):
> first defined here
> d000037.o:(.idata$6+0x0): multiple definition of `__nm___ZTISt9exception'
> /usr/lib/gcc/i686-pc-cygwin/4.3.2/libstdc++.dll.a(d002074.o):(.idata$6+0x0):
> first defined here
> d000073.o:(.idata$5+0x0): multiple definition of `__imp___ZTISt9exception'
> /usr/lib/gcc/i686-pc-cygwin/4.3.2/libstdc++.dll.a(d002074.o):(.idata$5+0x0):
> first defined here
> d000073.o:(.idata$6+0x0): multiple definition of `__nm___ZTISt9exception'
> /usr/lib/gcc/i686-pc-cygwin/4.3.2/libstdc++.dll.a(d002074.o):(.idata$6+0x0):
> first defined here
Ok, for some reason it appears that libCore.dll.a exports symbols from
libstdc++:
dkad...@ubik /work/root/test
$ nm /work/root/lib/libCore.dll.a |grep St9exception
71d6b958 d .rdata$_ZTISt9exception
71d6ff40 d .rdata$_ZTSSt9exception
71d6b958 D __ZTISt9exception
71d6ff40 D __ZTSSt9exception
Looks like the DLL got linked against static libstdc++, while the app links
against shared libstdc++? That certainly wouldn't be expected to work. I'll
take
a little look at how ROOT builds its DLLs, hopefully we just need to tweak an
LDFLAGS or similar somewhere.
cheers,
DaveK
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
