bug-libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool-2.2.11a on AIX 5.3 current git master 2010-08-25 /status


From: Ralf Wildenhues
Subject: Re: libtool-2.2.11a on AIX 5.3 current git master 2010-08-25 /status
Date: Mon, 20 Sep 2010 22:00:15 +0200
User-agent: Mutt/1.5.20 (2010-08-04)

[ adding libtool-patches ]

Hello Rainer, all,

* Rainer Tammer wrote on Sun, Sep 19, 2010 at 12:55:59PM CEST:
> here is the result of the bisect. I had to slightly change your
> suggested bisect script:
> 
> if grep 'FAIL: f[c7]*demo-exec' checklog; then
> ->
> if grep '^FAIL: ' checklog; then
> 
> Result:

> 2fc264a8e2f7224627bb7c191a38a2dc9e7b5bcb is first bad commit
> commit 2fc264a8e2f7224627bb7c191a38a2dc9e7b5bcb
> Author: Ralf Wildenhues <address@hidden>
> Date:   Fri Aug 6 22:03:19 2010 +0200
> 
>     Fix AC_NO_EXECUTABLES test failure on AIX.
> 
>     * libltdl/m4/libtool.m4 (_LT_SYS_MODULE_PATH_AIX): Wrap link
>     test in AC_CACHE_VAL, using cache variable $lt_cv_aix_libpath.
>     * tests/no-executables.at (AC_NO_EXECUTABLES): Preset it, to
>     avoid link test.
>     Bug report by Rainer Tammer.

Thank You! for carrying this through until the end!  The timing is
really at the last minute, before this becomes a regression in a
released version.

As far as I can see it, the semantic change of the above patch is that,
before the patch, _LT_SYS_MODULE_PATH_AIX computed the libpath value for
each compiler separately, while now it is done only once, by the C
compiler, and that result reused for the others.  A quick test reveals
that the different compilers add different directories to their path.

Now, The Right Thing[tm] would probably be to somehow merge these paths
intelligently, so that when we link C, C++, and Fortran code together,
all directories are available.  However, at this point I'm *only*
interested in avoiding *regressions* and still keeping the
no-executables issue fixed.

Thus, the attached patch uses, in addition to a global cache variable
(that the user may specify), a set of per-language cache variables.
(The trailing space in the tagvar name is because the CC tagvar has no
_CC suffix, but should not overlap with the global name.)

I'm running it on the AIX systems I have access to now.

Rainer, can you please try it on your problematic system, too, ASAP?

OK to commit?

Thanks,
Ralf

Attachment: 0001-Revert-to-per-language-libpath-computation-on-AIX.patch
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]