This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: g++ 3.2.x build problem


>>>>> Val Nets writes:

Val> Trying to build 3.2.2 on AIX/powerpc (3.2.1 had the same problem, but
Val> let's talk specific).
Val> Configured almost standard way, just giving my own --prefix and
Val> --enabling c,c++ langs only,
Val> and --disabled-shared (have my reasons):

Val> undefined reference to `typeinfo for std::bad_alloc'

Val> undefined reference to `vtable for __cxxabiv1::__si_class_type_info'

	These may be related to --disable-shared.

Val> P.S. while writing this message, got another experiment finished:
Val> configured the same way but without --disable-shared.
Val> this time, got assembler errors while compiling
Val> gcc-3.2.2/libstdc++-v3/src/globals.cc:
Val> /tmp//ccklu429.s: Assembler messages:
Val> /tmp//ccklu429.s:629: Error: unknown pseudo-op: `.symver'
Val> /tmp//ccklu429.s:637: Error: unknown pseudo-op: `.symver'
Val> /tmp//ccklu429.s:645: Error: unknown pseudo-op: `.symver'
Val> .... and so forth .... -- 20 of them

	Which assembler and linker are you using?  AIX as and AIX ld, or
using the GNUPro stuff from the AIX website?  You need to figure out why
the libstdc++ configuration is choosing to enable "versioning on shared
library symbols".  When I configure GCC on AIX, this defaults to "no".
you can manually force it to be disabled using --enable-symvers=no when
libstdc++ is configured, but it should not have been choosing "yes" on AIX
anyway.

	(By the way, you do not mention which version of AIX you are
using.)

David


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]