Re: automake config failure for autoconf test failure (poudriere based build activity)
Date: Tue, 16 Nov 2021 18:09:23 UTC
On 2021-Nov-16, at 08:42, Tijl Coosemans <tijl@FreeBSD.org> wrote: > On Sun, 14 Nov 2021 17:57:23 -0800 Mark Millard <marklmi@yahoo.com> > wrote: >> poudriere output: >> >> [00:24:23] [09] [00:01:20] Saved devel/automake | automake-1.16.4 wrkdir to: /usr/local/poudriere/data/wrkdirs/13_0R-CA72-default/default/automake-1.16.4.tbz >> [00:24:23] [09] [00:01:20] Finished devel/automake | automake-1.16.4: Failed: configure >> . . . >> >> logs/errors/automake-1.16.4.log : >> >> . . . >> checking whether autoconf is installed... yes >> checking whether autoconf works... no >> configure: error: The installed version of autoconf does not work. >> Please check config.log for error messages before this one. >> ===> Script "configure" failed unexpectedly. >> Please report the problem to tijl@FreeBSD.org [maintainer] and attach the >> "/wrkdirs/usr/ports/devel/automake/work/automake-1.16.4/config.log" including >> the output of the failure of your make command. Also, it might be a good idea >> to provide an overview of all packages installed on your system (e.g. a >> /usr/local/sbin/pkg-static info -g -Ea). >> *** Error code 1 >> >> Stop. >> make: stopped in /usr/ports/devel/automake >> =>> Cleaning up wrkdir >> ===> Cleaning for automake-1.16.4 >> build of devel/automake | automake-1.16.4 ended at Sun Nov 14 17:01:21 PST 2021 >> build time: 00:01:09 >> !!! build failure encountered !!! >> >> >> work/automake-1.16.4/config.log : >> >> . . . >> configure:3650: checking whether autoconf is installed >> configure:3656: autoconf --version >> autoconf (GNU Autoconf) 2.69 >> Copyright (C) 2012 Free Software Foundation, Inc. >> License GPLv3+/Autoconf: GNU GPL version 3 or later >> <http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html> >> This is free software: you are free to change and redistribute it. >> There is NO WARRANTY, to the extent permitted by law. >> >> Written by David J. MacKenzie and Akim Demaille. >> configure:3659: $? = 0 >> configure:3667: result: yes >> configure:3674: checking whether autoconf works >> configure:3684: cd conftest && autoconf -o /dev/null conftest.ac >> gm4:/usr/local/share/autoconf-2.69/autoconf/autoconf.m4f:1: expecting character `V' in frozen file >> autom4te-2.69: /usr/local/bin/gm4 failed with exit status: 1 >> configure:3687: $? = 1 >> configure:3696: result: no >> configure:3700: error: The installed version of autoconf does not work. >> Please check config.log for error messages before this one. >> . . . >> >> >> For reference: >> >> # uname -apKU >> FreeBSD CA72_16Gp_ZFS 14.0-CURRENT FreeBSD 14.0-CURRENT #19 main-n250667-20aa359773be-dirty: Sun Nov 14 02:57:32 PST 2021 root@CA72_16Gp_ZFS:/usr/obj/BUILDs/main-CA72-nodbg-clang/usr/main-src/arm64.aarch64/sys/GENERIC-NODBG-CA72 arm64 aarch64 1400042 1400042 >> >> # cd /usr/ports/ >> # ~/fbsd-based-on-what-commit.sh >> branch: main >> merge-base: 057c0c3c0645c0b237bb2a96dda440e0426ca983 >> merge-base: CommitDate: 2021-11-14 23:41:22 +0000 >> 057c0c3c0645 (HEAD -> main, freebsd/main, freebsd/HEAD) [NEW] security/snowflake-tor: Pluggable Transport using WebRTC inspired by Flashproxy >> n566061 (--first-parent --count for merge-base) >> >> >> Note(s): >> >> My amd64 FreeBSD context using the same sources (by content) did not >> have this problem. > > That's a strange error. Maybe try to rebuild m4 and autoconf packages. > On the FreeBSD package build cluster it builds fine. Here's the log > from today: > http://ampere2.nyi.freebsd.org/data/main-arm64-default/latest-per-pkg/automake-1.16.4.log On the FreebSD vintage involved, I seem to be getting fairly rare file corruptions during port builds in my aarch64 context. No retry of building a port that contained the corrupted file has produced a corruption in these cases. autoconf turned out to not be the only example: there were two others. (I've did multiple bulk -a runs back in October (for otehr reqsons) without evidence of corruptions. But bulk -a is not something I'd normally do and I did not keep the results. In this context between 400 and 500 port were built in each of 3 poudriere jails. 2 known corruptions in one jail's build, 1 in another, and one with no known corruptions.) So I got past the autoconf/automake problem but I've no clue how to set up a reproducible context for isolating what leads to having a corruption. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)