install.texi (*-ibm-aix*): Document assembler and achiver fixes required by libstdc++ and update...

* doc/install.texi (*-ibm-aix*): Document assembler and achiver
        fixes required by libstdc++ and update installation instructions
        for libstdc++.a.

From-SVN: r79401
This commit is contained in:
David Edelsohn 2004-03-12 18:45:24 +00:00 committed by David Edelsohn
parent b1f123c732
commit bb674cef28
2 changed files with 24 additions and 15 deletions

View File

@ -1,3 +1,9 @@
2004-03-12 David Edelsohn <edelsohn@gnu.org>
* doc/install.texi (*-ibm-aix*): Document assembler and achiver
fixes required by libstdc++ and update installation instructions
for libstdc++.a.
2004-03-12 Danny Smith <dannysmith@users.sourceforge.net>
* config/i386/winnt.c (i386_pe_strip_name_encoding_full): Strip

View File

@ -2906,35 +2906,38 @@ Assembler and Linker do not support AIX 5L sufficiently to bootstrap GCC.
The native AIX tools do interoperate with GCC@.
Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1). It also requires a
fix for another AIX Assembler bug and a co-dependent AIX Archiver fix
referenced as APAR IY53606 (AIX 5.2) or a APAR TBD (AIX 5.1)
@samp{libstdc++} in GCC 3.2 increments the major version number of the
@samp{libstdc++} in GCC 3.4 increments the major version number of the
shared object and GCC installation places the @file{libstdc++.a}
shared library in a common location which will overwrite the GCC 3.1
version of the shared library. Applications either need to be
re-linked against the new shared library or the GCC 3.1 version of the
@samp{libstdc++} shared object needs to be available to the AIX
runtime loader. The GCC 3.1 @samp{libstdc++.so.4} shared object can
be installed for runtime dynamic loading using the following steps to
set the @samp{F_LOADONLY} flag in the shared object for @emph{each}
shared library in a common location which will overwrite the and GCC
3.3 version of the shared library. Applications either need to be
re-linked against the new shared library or the GCC 3.1 and GCC 3.3
versions of the @samp{libstdc++} shared object needs to be available
to the AIX runtime loader. The GCC 3.1 @samp{libstdc++.so.4}, if
present, and GCC 3.3 @samp{libstdc++.so.5} shared objects can be
installed for runtime dynamic loading using the following steps to set
the @samp{F_LOADONLY} flag in the shared object for @emph{each}
multilib @file{libstdc++.a} installed:
Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
archive:
Extract the shared objects from the currently installed
@file{libstdc++.a} archive:
@smallexample
% ar -x libstdc++.a libstdc++.so.4
% ar -x libstdc++.a libstdc++.so.4 libstdc++.so.5
@end smallexample
Enable the @samp{F_LOADONLY} flag so that the shared object will be
available for runtime dynamic loading, but not linking:
@smallexample
% strip -e libstdc++.so.4
% strip -e libstdc++.so.4 libstdc++.so.5
@end smallexample
Archive the runtime-only shared object in the GCC 3.2
Archive the runtime-only shared object in the GCC 3.4
@file{libstdc++.a} archive:
@smallexample
% ar -q libstdc++.a libstdc++.so.4
% ar -q libstdc++.a libstdc++.so.4 libstdc++.so.5
@end smallexample
Linking executables and shared libraries may produce warnings of