http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52623
--- Comment #11 from Michael Haubenwallner <michael.haubenwallner at salomon
dot at> 2012-03-23 09:31:41 UTC ---
Unless IBM does, I don't want to change any default here, nor force anyone to
use -brtl.
What I'm after is:
Give package managers another choice how to build the packages, out of:
A: libNAME.a(libNAME.so.1) (libtool default)
B: libNAME.so (supported by libtool)
C: libNAME.so.1(shr.o) (new)
Using autoconf+libtool, the variants could be selected using:
A : default (same as --disable-aix-svr4)
A B : LDFLAGS=-Wl,-brtl
B : LDFLAGS=-Wl,-brtl --disable-static
A C: --enable-aix-svr4
C: --enable-aix-svr4 --disable-static
(*able-aix-svr4 feels more correct than *able-aix-soname)
For the FLOSS developers:
Most of them don't care AIX (among others) at all. However, they use libtool
(or something else) that allows them to not care.
For XLC:
There is nothing specific to GCC, Import Files work with XLC too, and I don't
want to change anything within collect2 or GNU-ld - just the build-scripts
(libtool&co).
For multilib:
I've seen package managers building a package twice, and merge both
"(libNAME.so.1)" into "libNAME.a".
This works for A as well as C, but does not work for B.
(In reply to comment #10)
> An additional problem is Binutils "strip" command does not support the -e/-E
> command line option to set F_LOADONLY.
This should be fixed anyway.
