http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52623
--- Comment #13 from Michael Haubenwallner <michael.haubenwallner at salomon
dot at> 2012-03-23 16:39:53 UTC ---
Hmm, err, A and B aren't created at the same time by libtool.
Instead, this table really should include static-only libs too:
(S)tatic: libNAME.a(static.o)
(A)ix: libNAME.a(libNAME.so.1)
(B)roken: libNAME.so
(L)inux: libNAME.so.1(shr.o)
| (default:yes) | (default:yes) | (default:no) | (default:"") |
| enable-static | enable-shared | enable-aix-svr4 | LDFLAGS |
--+------+---------------+---------------+-----------------+--------------+
1 | S : yes | no | irrelevant | irrelevant |
2 | A : yes | yes | no | "" |
3 | S B : yes | yes | no | "-brtl" |
4 | B : no | yes | no | "-brtl" |
5 | A L : yes | yes | compat | irrelevant |
6 | S L : yes | yes | yes | irrelevant |
7 | L : no | yes | yes | irrelevant |
--+------+---------------+---------------+-----------------+--------------+
Besides shared and/or static, package managers would have a choice of three:
1 and 2: traditional AIX only
(3 and 4: broken)
5 : SVR4 with compatibility to traditional AIX
6 and 7: SVR4 only
But - first of all:
Besides those administrative issues, do you see any technical issue why Import
Files cannot be used this way for filename-based versioning over the
traditional onefile-membername-based versioning?
