GNU bug report logs - #19893
GNU libtool-2.4.6 released [stable]

Previous Next

To reply to this bug, email your comments to 19893 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Michael Felt <aixtools <at> gmail.com>
To: bug-libtool <at> gnu.org
Subject: Re: GNU libtool-2.4.6 released [stable]
Date: Wed, 18 Feb 2015 09:18:51 +0100

[Message part 1 (text/plain, inline)]

Build proceeded without incident - running make check returns some errors -
but maybe these are with the test, not libtool.

Test 70, e.g., proceeds fine but at line 61 - it fails - after having done
the hard work perhaps, and I suspect because $GREP is not defined

in the test file runpath-in-lalib.at

   +61  AT_CHECK([$GREP /foobar $libdir/liba.la], [], [ignore])
   +62  AT_CHECK([$GREP /foobar $libdir/libb.la], [], [ignore])
   +63
   +64  # TODO: check that m gets -R, too.
   +65
   +66  AT_CLEANUP

In the log file:
./runpath-in-lalib.at:59: $LIBTOOL --mode=install cp m$EXEEXT
$bindir/m$EXEEXT
stderr:
stdout:
libtool: install: cp .libs/m
/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.d
ir/070/inst/bin/m
./runpath-in-lalib.at:61: $GREP /foobar $libdir/liba.la
stdout:
./runpath-in-lalib.at:61: exit code was 1, expected 0
70. runpath-in-lalib.at:25: 70. Runpath in libtool library files
(runpath-in-lalib
.at:25): FAILED (runpath-in-lalib.at:61)

Two questions:

1. the word [ignore] at the end does not mean to ignore exit status - I am
guessing. So what does it mean?
2. How can I easily run a (verbose) single-test (and maybe have it echo the
values of things like $GREP)

Addition:
I am running the tests against 'coreutils' rather than standard AIX - I
should (and will) repeat the tests without coreutils - maybe even 'real
soon' rather than eventually :)
root <at> x064:[/data/prj/gnu/libtool/libtool-2.4.6/tests]type cp
cp is a tracked alias for /opt/bin/cp
root <at> x064:[/data/prj/gnu/libtool/libtool-2.4.6/tests]type install
install is /opt/bin/install

I mention (and do) this because AIX /usr/bin/install (and even the AIX
/usr/bsd/install) fail sometimes (with some projects, e.g. httpd).



On Sun, Feb 15, 2015 at 10:03 PM, Gary V. Vaughan <gary <at> gnu.org> wrote:

> Libtoolers!
>
> The Libtool Team is pleased to announce the release of libtool 2.4.6.
>
> GNU Libtool hides the complexity of using shared libraries behind a
> consistent, portable interface. GNU Libtool ships with GNU libltdl, which
> hides the complexity of loading dynamic runtime libraries (modules)
> behind a consistent, portable interface.
>
> This is a bugfix release, and a recommended upgrade for all users.  Most
> importantly, it regains most of the speed of 2.4.2 by correcting one of
> two known regressions that were causing noticable slow-down when building
> projects with many source files.
>
> Here are the compressed sources:
>   http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz   (1.7MB)
>   http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.xz   (952KB)
>
> Here are the GPG detached signatures[*]:
>   http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.gz.sig
>   http://ftpmirror.gnu.org/libtool/libtool-2.4.6.tar.xz.sig
>
> Use a mirror for higher download bandwidth:
>   http://www.gnu.org/order/ftp.html
>
> [*] Use a .sig file to verify that the corresponding file (without the
> .sig suffix) is intact.  First, be sure to download both the .sig file
> and the corresponding tarball.  Then, run a command like this:
>
>   gpg --verify libtool-2.4.6.tar.gz.sig
>
> If that command fails because you don't have the required public key,
> then run this command to import it:
>
>   gpg --keyserver keys.gnupg.net --recv-keys 151308092983D606
>
> and rerun the 'gpg --verify' command.
>
> This release was bootstrapped with the following tools:
>   Autoconf 2.69
>   Automake 1.15
>   Gnulib v0.1-336-g342d9f0
>
> NEWS
>
> * Noteworthy changes in release 2.4.6 (2015-02-15) [stable]
>
> ** New features:
>
>   - LT_SYS_LIBRARY_PATH can be set in config.site, or at configure time
>     and persists correctly in the generated libtool script.
>
> ** Bug fixes:
>
>   - Fix a race condition in ltdl dryrun test that would cause spurious
>     random failures of that test.
>
>   - LT_SYS_DLSEARCH_PATH is munged correctly.
>
>
> Enjoy!
>
>
> --
> If you have a working or partly working program that you'd like
> to offer to the GNU project as a GNU package, see
> https://www.gnu.org/help/evaluation.html.
>

[Message part 2 (text/html, inline)]

Message #8 received at 19893 <at> debbugs.gnu.org (full text, mbox):

From: Nick Bowler <nbowler <at> elliptictech.com>
To: Michael Felt <aixtools <at> gmail.com>
Cc: 19893 <at> debbugs.gnu.org
Subject: Re: bug#19893: GNU libtool-2.4.6 released [stable]
Date: Wed, 18 Feb 2015 09:46:31 -0500

Hi,

I don't know about the specific failure but I can answer your
questions...

On 2015-02-18 09:18 +0100, Michael Felt wrote:
> Test 70, e.g., proceeds fine but at line 61 - it fails
[...]
> in the test file runpath-in-lalib.at
> 
>    +61  AT_CHECK([$GREP /foobar $libdir/liba.la], [], [ignore])
>    +62  AT_CHECK([$GREP /foobar $libdir/libb.la], [], [ignore])
>    +63
>    +64  # TODO: check that m gets -R, too.
>    +65
>    +66  AT_CLEANUP
[...]
> Two questions:
> 
> 1. the word [ignore] at the end does not mean to ignore exit status - I am
> guessing. So what does it mean?

It means to ignore the standard output of the command (not completely;
it is still recorded in the testsuite log file).

> 2. How can I easily run a (verbose) single-test (and maybe have it echo the
> values of things like $GREP)

You can pass flags to the testsuite by setting TESTSUITEFLAGS, e.g.,

  make check TESTSUITEFLAGS='70'

to run just test 70.  See ./tests/testsuite --help for more testsuite
options; perhaps --trace will be helpful for you.

Regards,
-- 
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)

Message #11 received at 19893 <at> debbugs.gnu.org (full text, mbox):

From: Michael Felt <aixtools <at> gmail.com>
To: Nick Bowler <nbowler <at> elliptictech.com>
Cc: 19893 <at> debbugs.gnu.org
Subject: Re: bug#19893: GNU libtool-2.4.6 released [stable]
Date: Thu, 19 Feb 2015 19:09:55 +0100

[Message part 1 (text/plain, inline)]

thanks.
On Feb 18, 2015 3:46 PM, "Nick Bowler" <nbowler <at> elliptictech.com> wrote:

> Hi,
>
> I don't know about the specific failure but I can answer your
> questions...
>
> On 2015-02-18 09:18 +0100, Michael Felt wrote:
> > Test 70, e.g., proceeds fine but at line 61 - it fails
> [...]
> > in the test file runpath-in-lalib.at
> >
> >    +61  AT_CHECK([$GREP /foobar $libdir/liba.la], [], [ignore])
> >    +62  AT_CHECK([$GREP /foobar $libdir/libb.la], [], [ignore])
> >    +63
> >    +64  # TODO: check that m gets -R, too.
> >    +65
> >    +66  AT_CLEANUP
> [...]
> > Two questions:
> >
> > 1. the word [ignore] at the end does not mean to ignore exit status - I
> am
> > guessing. So what does it mean?
>
> It means to ignore the standard output of the command (not completely;
> it is still recorded in the testsuite log file).
>
> > 2. How can I easily run a (verbose) single-test (and maybe have it echo
> the
> > values of things like $GREP)
>
> You can pass flags to the testsuite by setting TESTSUITEFLAGS, e.g.,
>
>   make check TESTSUITEFLAGS='70'
>
> to run just test 70.  See ./tests/testsuite --help for more testsuite
> options; perhaps --trace will be helpful for you.
>
> Regards,
> --
> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
>

[Message part 2 (text/html, inline)]

Message #14 received at 19893 <at> debbugs.gnu.org (full text, mbox):

From: Michael Felt <aixtools <at> gmail.com>
To: Nick Bowler <nbowler <at> elliptictech.com>
Cc: 19893 <at> debbugs.gnu.org
Subject: Re: bug#19893: GNU libtool-2.4.6 released [stable]
Date: Wed, 25 Feb 2015 16:52:15 +0100

[Message part 1 (text/plain, inline)]

OK - it took awhile to understand this test - and I think it does indicate
a bug.

If I understand the test it is expecting the directory
addrunpath=`pwd`/foobar to be added to the .la file (and now I understand
the name of the test :)) -- tests/runpath-in-lalib.at

I expect this is to 'happen' with this statement

AT_CHECK([$LIBTOOL --mode=link $CC $CFLAGS $LDFLAGS -o liba.la a.lo -rpath
$libdir -R$addrunpath],
         [], [ignore], [ignore])

At the end of the test - this is the contents of the .la files regarding
libraries:
root <at> x064:[/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070]tail
-3 liba.la

# Directory that this library needs to be installed in:
libdir='/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070/inst/lib'

root <at> x064:[/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070]tail
-3 libb.la
# Directory that this library needs to be installed in:
libdir='/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070/inst/lib'
relink_command="(cd
/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070; /bin/sh
\"/data/prj/gnu/libtool/libtool-2.4.6/libtool\"  --mode=relink cc -O2
-qlanglvl=extc99 -o libb.la b.lo -rpath
/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070/inst/lib liba.la
@inst_prefix_dir@)"

Looking at the .so.0 files though...

root <at> x064:[/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070]dump
-H .libs/liba.so.0 | tail -3
                        ***Import File Strings***
INDEX  PATH                          BASE
MEMBER
0
/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070/foobar:/usr/vac/lib:/usr/lib:/lib


root <at> x064:[/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070]dump
-H .libs/libb.so.0 | tail -4
                        ***Import File Strings***
INDEX  PATH                          BASE
MEMBER
0
/data/prj/gnu/libtool/libtool-2.4.6/tests/testsuite.dir/070/inst/lib:/usr/vac/lib:/usr/lib:/lib

1                                    liba.a
liba.so.0

We see that .../foobar has been added to the internal LIBPATH variable.

I am a bit surprised by this because -R is suppossed to be a NULL op unless
the -bsvr4 flag is also specified - maybe that is also heppening in the
background - will look more carefully for that.

In any case, .../foobar is getting added to the shared object, but not the
.la text.

I have no clue where to look beyond this - hints/patch is welcome!

Michael





On Thu, Feb 19, 2015 at 7:09 PM, Michael Felt <aixtools <at> gmail.com> wrote:

> thanks.
> On Feb 18, 2015 3:46 PM, "Nick Bowler" <nbowler <at> elliptictech.com> wrote:
>
>> Hi,
>>
>> I don't know about the specific failure but I can answer your
>> questions...
>>
>> On 2015-02-18 09:18 +0100, Michael Felt wrote:
>> > Test 70, e.g., proceeds fine but at line 61 - it fails
>> [...]
>> > in the test file runpath-in-lalib.at
>> >
>> >    +61  AT_CHECK([$GREP /foobar $libdir/liba.la], [], [ignore])
>> >    +62  AT_CHECK([$GREP /foobar $libdir/libb.la], [], [ignore])
>> >    +63
>> >    +64  # TODO: check that m gets -R, too.
>> >    +65
>> >    +66  AT_CLEANUP
>> [...]
>> > Two questions:
>> >
>> > 1. the word [ignore] at the end does not mean to ignore exit status - I
>> am
>> > guessing. So what does it mean?
>>
>> It means to ignore the standard output of the command (not completely;
>> it is still recorded in the testsuite log file).
>>
>> > 2. How can I easily run a (verbose) single-test (and maybe have it echo
>> the
>> > values of things like $GREP)
>>
>> You can pass flags to the testsuite by setting TESTSUITEFLAGS, e.g.,
>>
>>   make check TESTSUITEFLAGS='70'
>>
>> to run just test 70.  See ./tests/testsuite --help for more testsuite
>> options; perhaps --trace will be helpful for you.
>>
>> Regards,
>> --
>> Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
>>
>

[Message part 2 (text/html, inline)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.