GNU bug report logs - #25615
make -k check (expected failure)

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 25615 in the body.
You can then email your comments to 25615 AT debbugs.gnu.org in the normal way.

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

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

From: Frederic Peugny <frederic.peugny <at> gmail.com>
To: bug-libtool <at> gnu.org
Subject: make -k check (expected failure)
Date: Fri, 3 Feb 2017 20:21:36 +0100

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

Hello,
I have installed libtool-2.4.6 from source (tar.gz)
I'm trying now to follow the steps of the howto "Using libtool" on the gnu
homepage. However I had to copy and paste the contents of the following
files from the libtool-2.4.6/tests/demo.at m4 script:
 + main.c
 + hello.c
 + foo.c
 + hell1.c
 + hell2.c
 + dlmain.c

because I cannot them directly nor a demo/ subdirectory.
The problem is that I can generate up to the libhello.la file but cannot go
further.
It must be related that all the tests steps of the 'make -k check' (see the
log in attachment) are declared as "(expected failure demo.at(xxx))".
Can see something I have missed in the installation?

-- 
Frédéric Peugny

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

[testsuite.log (application/octet-stream, attachment)]

Message #10 received at 25615-done <at> debbugs.gnu.org (full text, mbox):

From: Ileana Dumitrescu <ileanadumitrescu95 <at> gmail.com>
To: 25615-done <at> debbugs.gnu.org
Cc: Frederic Peugny <frederic.peugny <at> gmail.com>
Subject: Re: bug#25615: make -k check (expected failure)
Date: Mon, 21 Oct 2024 21:14:09 +0300

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

You are right that there is no demo/ subdirectory, but the documentation
should be updated to remove all instances of it now. Users can generate
output from the Autotests by passing "--debug" or "-d" to make check
with the variable TESTSUITEFLAGS [1]. The test output can be found in
tests/testsuite.dir/<test_number>, where test_number is the test you
are debugging.

[1] 
https://git.savannah.gnu.org/cgit/libtool.git/commit/?id=2048edd2cba086b194bd30901e5fe552a4890680

-- 
Ileana Dumitrescu

GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354

[OpenPGP_0x6570EA01146F7354.asc (application/pgp-keys, attachment)]

[OpenPGP_signature.asc (application/pgp-signature, attachment)]

Previous Next

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