[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
several AIX questions
From: |
Ralf Wildenhues |
Subject: |
several AIX questions |
Date: |
Sun, 20 Nov 2005 20:08:50 +0100 |
User-agent: |
Mutt/1.5.9i |
1) This patch from HEAD:
| 2004-09-26 Albert Chin-A-Young <address@hidden>
|
| * m4/libtool.m4 (_LT_LINKER_SHLIBS) [aix]: In archive_expsym_cmds,
| move -bnoentry linker option before $compiler_flags to honor any
| possible -e entries in LDFLAGS.
http://lists.gnu.org/archive/html/libtool-patches/2004-09/msg00321.html
has been applied to the C case only (and not backported to branch-1-5).
Should it not be for C++ as well? What's the reason for it anyway?
Also, should it not also be applied to the ia64 case?
2) One of the comments in libtool.m4:
| On ia64, ld does runtimelinking by default.
Is it possible to turn this off on ia64? Even if, is it worthwhile to
support so in Libtool? If not: let's simplify AIX support in libtool.m4.
The libtool.m4 snippets for aix[45] look like they've been expanded too
much (rtl-or-ia64 case vs not should not be handled twice; and they
actually look like they had been unified at some point in the past).
3) This thing has me stunned (non-rtl case): mdemo-exec on *uninstalled*
modules works, whereas on *installed* ones it fails; reason: we don't
install the .so files. We
ar cru libfoo.a libfoo.so.0
and then install libfoo.a only. What's the right way to fix this?
Install libfoo.so.0 as well? Is there maybe some root-only trickery
necessary so that the installed .so file isn't necessary (I think not)?
4) Will multiple dlopen()ing of a module give separate instances of
static variables, if the module has not been -brtl'ed? We need a test
for this.
Cheers,
Ralf
- several AIX questions,
Ralf Wildenhues <=