AIX install.texi update

[David Edelsohn]

        * doc/install.texi (*-ibm-aix*): Explain AIX shared object versioning.

Index: install.texi
===================================================================
RCS file: /cvs/gcc/egcs/gcc/doc/install.texi,v
retrieving revision 1.131
diff -c -p -r1.131 install.texi
*** install.texi	8 Aug 2002 09:10:39 -0000	1.131
--- install.texi	16 Aug 2002 17:21:50 -0000
*************** interoperate with GCC@.
*** 2337,2342 ****
--- 2337,2371 ----
  Building @file{libstdc++.a} requires a fix for an AIX Assembler bug
  APAR IY26685 (AIX 4.3) or APAR IY25528 (AIX 5.1).
  
+ @samp{libstdc++} in GCC 3.2 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}
+ multilib @file{libstdc++.a} installed:
+ 
+ Extract the shared object from each the GCC 3.1 @file{libstdc++.a}
+ archive:
+ @example
+    % ar -x libstdc++.so.4 libstdc++.a
+ @end example
+ 
+ Enable the @samp{F_LOADONLY} flag so that the shared object will be
+ available for runtime dynamic loading, but not linking:
+ @example
+    % strip -e libstdc++.so.4
+ @end example
+ 
+ Archive the runtime-only shared object in the GCC 3.2
+ @file{libstdc++.a} archive:
+ @example
+    % ar -q libstdc++.so.4 libstdc++.a
+ @end example
+ 
  Linking executables and shared libraries may produce warnings of
  duplicate symbols.  The assembly files generated by GCC for AIX always
  have included multiple symbol definitions for certain global variable