Re: [GNU Autoconf 2.73.7-528c] testsuite: 293 300 failed

Sean Denney via Bug reports for autoconf <[email protected]> Fri, 15 May 2026 08:53:19 +0200
Newsgroups gmane.comp.sysutils.autoconf.bugs
Message-ID <[email protected]>
I=E2=80=99ve compiled libtool from the 2.5.4 release, but the same two =
tests fail in autoconf. I can=E2=80=99t figure out how to do a diff =
between your fedora rpms and the gnu libtool git repository. The only =
test that fails when running a check on libtool is C++ exception =
handling (test 146). Commenting out the single line in exceptions.at:398 =
<http://exceptions.at:398/> and the tests proceed fine.

As for the two tests that fail in autoconf:

293: Package requiring libtool                       FAILED =
(torture.at:2076)
300: autoreconf --exclude (libtoolize)               FAILED =
(torture.at:2405)

Here are the specific test logs:

293. torture.at:2037: testing Package requiring libtool ...
./torture.at:2075: autoreconf -Wall -v -i
stderr:
autoreconf: export WARNINGS=3Dall
autoreconf: Entering directory '.'
autoreconf: configure.ac: no obvious need to run autopoint
autoreconf: running: aclocal =
--system-acdir=3D/Users/sdenney/Downloads/00_libraries/K/J001_GNU_Autoconf=
/autoconf/tests/at_empty_dir -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: configure.ac: not using Intltool
autoreconf: configure.ac: not using Gtkdoc
autoreconf: configure.ac: no need to run autopoint (confirmed)
autoreconf: running: autoconf =
--prepend-include=3D/Users/sdenney/Downloads/00_libraries/K/J001_GNU_Autoc=
onf/autoconf/lib =
--prepend-include=3D/Users/sdenney/Downloads/00_libraries/K/J001_GNU_Autoc=
onf/autoconf/lib
autoreconf: configure.ac: not running autoheader: no config headers
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'
autoreconf: configure.ac: not running make: --make not given
autoreconf: Leaving directory '.'
stdout:
./torture.at:2076: $EGREP 'running: .*libtoolize' stderr
stderr:
stdout:
./torture.at:2076: exit code was 1, expected 0
293. torture.at:2037: 293. Package requiring libtool (torture.at:2037): =
FAILED (torture.at:2076)


300. torture.at:2369: testing autoreconf --exclude (libtoolize) ...
./torture.at:2403: autoreconf -Wall -v -i --exclude libtoolize
stderr:
autoreconf: export WARNINGS=3Dall
autoreconf: Entering directory '.'
autoreconf: configure.ac: no obvious need to run autopoint
autoreconf: running: aclocal =
--system-acdir=3D/Users/sdenney/Downloads/00_libraries/K/J001_GNU_Autoconf=
/autoconf/tests/at_empty_dir -I m4
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not using Libtool
autoreconf: configure.ac: not using Intltool
autoreconf: configure.ac: not using Gtkdoc
autoreconf: configure.ac: no need to run autopoint (confirmed)
autoreconf: running: autoconf =
--prepend-include=3D/Users/sdenney/Downloads/00_libraries/K/J001_GNU_Autoc=
onf/autoconf/lib =
--prepend-include=3D/Users/sdenney/Downloads/00_libraries/K/J001_GNU_Autoc=
onf/autoconf/lib
autoreconf: configure.ac: not running autoheader: no config headers
autoreconf: running: automake --add-missing --copy --no-force
configure.ac:3: installing './install-sh'
configure.ac:3: installing './missing'
autoreconf: configure.ac: not running make: --make not given
autoreconf: Leaving directory '.'
stdout:
./torture.at:2403: exit code was 0, expected 1
300. torture.at:2369: 300. autoreconf --exclude (libtoolize) =
(torture.at:2369): FAILED (torture.at:2403)


Thanks
=E2=80=94 Sean

> On May 12, 2026, at 7:00=E2=80=AFPM, Paul Eggert <[email protected]> =
wrote:
>=20
> On 2026-05-11 19:13, Sean Denney via Bug reports for autoconf wrote:
>> See attached for the testsuite.log file.
>=20
> Nothing was attached, unfortunately. An archive of your email is here:
>=20
> https://lists.gnu.org/r/bug-autoconf/2026-05/msg00001.html
>=20
> Not sure the testsuite.log file would help much, though.
>=20
> Since your test failures are libtool-related, and since you're using =
"GNU libtool 2.5.4.3-b341-dirty", it's probably something to do with =
that "-b341-dirty". I don't see a problem when using your recipe on =
Fedora 44, which is running libtool.x86_64 2.5.4-10.fc44, so perhaps you =
can compare Fedora 44's libtool source to your libtool source.
>=20
> https://packages.fedoraproject.org/pkgs/libtool/libtool/