From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (ff4b1fc) for armv6l on arm64-01.zrh.ipfire.org
Date: Thu, 11 Aug 2022 01:54:33 +0000 [thread overview]
Message-ID: <4M38xj397Rz21GG@arm64-01.zrh.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]
https://nightly.ipfire.org/next/2022-08-10%2021%3A04%3A36%20%2B0000-ff4b1fc1/armv6l
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=ff4b1fc1306f1e5f90fbbbe04c54f19517ea05ac
Packaged toolchain compilation
Checking for necessary space on disk [ DONE ]
Set cache size limit to 4.0 GB
Building LFS
stage2 [ 1 ][ DONE ]
linux (5.15.59) KCFG=-headers [ 1:25 ][ DONE ]
man-pages (5.13) [ 8 ][ DONE ]
glibc (2.35) [ 9:46 ][ DONE ]
tzdata (2022a) [ 3 ][ DONE ]
cleanup-toolchain [ 0 ][ DONE ]
zlib (1.2.12) [ 1 ][ DONE ]
zstd (1.5.2) [ 2 ][ DONE ]
autoconf (2.71) [ 2 ][ DONE ]
automake (1.16.3) [ 3 ][ DONE ]
libtool (2.4.6) [ 0 ][ FAIL ]
chmod +x '/usr/share/automake-1.16/mkinstalldirs'
chmod +x '/usr/share/automake-1.16/ylwrap'
chmod +x '/usr/share/automake-1.16/depcomp'
chmod +x '/usr/share/automake-1.16/compile'
chmod +x '/usr/share/automake-1.16/py-compile'
chmod +x '/usr/share/automake-1.16/ar-lib'
chmod +x '/usr/share/automake-1.16/test-driver'
chmod +x '/usr/share/automake-1.16/tap-driver.sh'
make[3]: Leaving directory '/usr/src/automake-1.16.3'
make[2]: Leaving directory '/usr/src/automake-1.16.3'
make[1]: Leaving directory '/usr/src/automake-1.16.3'
Updating linker cache...
Install done; saving file list to /usr/src/log/automake-1.16.3 ...
Aug 11 01:54:32: Building libtool libtool-2.4.6.tar.xz checksum OK
+ cd /usr/src/lfs
+ make -f libtool LFS_BASEDIR=/usr/src install
====================================== Installing libtool-2.4.6 ...
Install started; saving file list to /usr/src/lsalr ...
cd /usr/src/libtool-2.4.6 && ./configure \
--prefix=/usr
## ------------------------- ##
## Configuring libtool 2.4.6 ##
## ------------------------- ##
checking for GNU M4 that supports accurate traces... configure: error: no acceptable m4 could be found in $PATH.
GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
GNU M4 1.4.15 uses a buggy replacement strstr on some systems.
Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another strstr bug.
make: *** [libtool:79: /usr/src/log/libtool-2.4.6] Error 1
ERROR: Building libtool [ FAIL ]
Check /build/nightly/next/log/_build.base.log for errors if applicable[ FAIL ]
reply other threads:[~2022-08-11 1:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4M38xj397Rz21GG@arm64-01.zrh.ipfire.org \
--to=nightly-builds@ipfire.org \
--cc=nightly-builds@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox