Re: [PATCH 1/2] Use POSIX nm to simplify AIX export_symbols_cmds.

2016-03-21 Thread Michael Haubenwallner
On 03/20/2016 01:04 AM, David Edelsohn wrote: > I agree with this in principle, but I'm not convinced that the patch > itself is correct. Thanks! > I also would have split the MS-compatible part of the patch as a > separate step. It is not listed in the ChangeLog and just confuses > the patch.

Re: [PATCH 1/2] Use POSIX nm to simplify AIX export_symbols_cmds.

2016-03-21 Thread David Edelsohn
On Mon, Mar 21, 2016 at 4:49 AM, Michael Haubenwallner wrote: > > On 03/20/2016 01:04 AM, David Edelsohn wrote: >> I agree with this in principle, but I'm not convinced that the patch >> itself is correct. > > Thanks! > >> I also would have split the MS-compatible part of the patch as a >> separat

Re: [PATCH 1/2] Use POSIX nm to simplify AIX export_symbols_cmds.

2016-03-21 Thread Michael Haubenwallner
On 03/21/2016 03:47 PM, David Edelsohn wrote: > On Mon, Mar 21, 2016 at 4:49 AM, Michael Haubenwallner > wrote: >> >> On 03/20/2016 01:04 AM, David Edelsohn wrote: >>> I agree with this in principle, but I'm not convinced that the patch >>> itself is correct. >> >> Thanks! >> >>> I also would hav

[PATCH 0/3, updated] AIX-driven support for POSIX nm

2016-03-21 Thread Michael Haubenwallner
Hi, 've reworked the AIX driven patches based on the discussion around patch "[3/4] Use POSIX nm to simplify AIX export_symbols_cmds." http://lists.gnu.org/archive/html/libtool-patches/2016-03/msg00016.html Previous patch "[1/4] Fix func_echo_all inside configure." is not required any more, altho

[PATCH 1/3] AIX: use proper ABI flags in search for toolchain

2016-03-21 Thread Michael Haubenwallner
The native PowerPC AIX toolchain does accept only 32 bit objects by default. They either need the -X32_64 flag to accept both, or the OBJECT_MODE=64 environment variable to accept 64 bit only. We rely on the new gl_POWERPC_AIX_OBJECT_MODE early gnulib macro setting the gl_cv_powerpc_aix_object_mo

[PATCH 3/3] AIX: Stop exporting any _GLOBAL__ symbol.

2016-03-21 Thread Michael Haubenwallner
* m4/libtool.m4 (_LT_LINKER_SHLIBS): On AIX, GNU g++ generates _GLOBAL__* symbols as, amongst others, landing pads for C++ exceptions. These symbols must not be exported from shared libraries, or exception handling may break for applications with runtime linking enabled. --- m4/libtool.m4 | 2 ++

[PATCH 2/3] support POSIX nm, prefer POSIX nm for AIX

2016-03-21 Thread Michael Haubenwallner
In BSD mode, the AIX nm does not tell whether a symbol is weak, we need to use POSIX mode instead. * m4/libtool.m4 (LT_PATH_NM): For AIX, search for nm supporting the -P flag (POSIX mode). When AIX nm is found, add the -C and -l flags. Add detection of POSIX compatible nm. (_LT_CMD_GLOBAL_SYMBOLS

Re: [PATCH 1/2] Use POSIX nm to simplify AIX export_symbols_cmds.

2016-03-21 Thread David Edelsohn
On Mon, Mar 21, 2016 at 12:50 PM, Michael Haubenwallner wrote: > > On 03/21/2016 03:47 PM, David Edelsohn wrote: >> On Mon, Mar 21, 2016 at 4:49 AM, Michael Haubenwallner >> wrote: >>> >>> On 03/20/2016 01:04 AM, David Edelsohn wrote: I agree with this in principle, but I'm not convinced tha

Re: [PATCH 2/2] AIX: Stop exporting any _GLOBAL__ symbol.

2016-03-21 Thread David Edelsohn
On Wed, Mar 2, 2016 at 11:19 AM, Michael Haubenwallner wrote: > * m4/libtool.m4 (_LT_LINKER_SHLIBS): On AIX, GNU g++ generates > _GLOBAL__* symbols as, amongst others, landing pads for C++ exceptions. > These symbols must not be exported from shared libraries, or exception > handling may break for