http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52447
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |i?86-*-*
--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-01
12:05:29 UTC ---
(In reply to comment #4)
> Can you confirm that applications built on Red Hat with:
>
> Reading specs from /usr/lib/gcc/i386-redhat-linux/3.4.6/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> --disable-libunwind-exceptions --enable-java-awt=gtk --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.4.6 20060404 (Red Hat 3.4.6-11)
>
> should work on SLES 11 with the standard libstdc++ on that system which is
> 6.0.10? Or do we need to ensure that 6.0.8 is used?
SLE11 SP1 gcc is configured like
../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man
--libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3
--enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/
'--with-pkgversion=SUSE Linux' --disable-libgcj --disable-libmudflap
--with-slibdir=/lib --with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --program-suffix=-4.3
--enable-linux-futex --without-system-libunwind --with-cpu=generic
--build=i586-suse-linux
which looks compatible. So yes, it should work.
I am assuming you are on a 32bit host. Please clarify if you built
on a 32bit host but are running on a 64bit host with 32bit libs.
> Producing a test case will be hard because it is a large application using
> many
> shared libraries.
It might be that the new libstdc++ uses TLS for thread-safe init and the
old one not and that you are hitting a dynamic linker bug so that TLS is
not properly initialized when the application dlopens libmuwssoap.so.
You have to debug this further yourself if you do not have a testcase.
