This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libstdc++/23406] libstdc++ fails to link with std::string on AIX
- From: "michael dot haubenwallner at salomon dot at" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Dec 2005 11:22:17 -0000
- Subject: [Bug libstdc++/23406] libstdc++ fails to link with std::string on AIX
- References: <bug-23406-7959@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #7 from michael dot haubenwallner at salomon dot at 2005-12-01 11:22 -------
Just for completion:
The problem is not GNU ar, but GNU nm.
libstdc++ does not work when built with GNU nm, but works when built with AIX
nm (always without GNU as/ld, but with GNU ar/objdump/ranlib/strip).
I've compared build-outputs of gcc-3.4.4 with and without GNU nm, and found
this:
when "generating symbol list for `libstdc++.la'", GNU nm says:
BFD: .libs/allocator-inst.o: warning: illegal symbol index 0 in line numbers
BFD: .libs/allocator-inst.o: warning: illegal symbol index 0 in line numbers
This happens for
powerpc-ibm-aix5.2.0.0/libstdc++-v3
powerpc-ibm-aix5.2.0.0/pthread/libstdc++-v3
but not for
powerpc-ibm-aix5.2.0.0/ppc64/libstdc++-v3
powerpc-ibm-aix5.2.0.0/pthread/ppc64/libstdc++-v3
It's the same for both binutils-2.16 and 2.16.1.
So - i'll consider comment#6.
--
michael dot haubenwallner at salomon dot at changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michael dot haubenwallner at
| |salomon dot at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23406