From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: Nightly Builds List <nightly-builds@lists.ipfire.org>
Subject: [FAILED] Nightly Build of next (30cae58) for x86_64 on x86-01.haj.ipfire.org
Date: Sat, 09 Aug 2025 00:00:27 +0000 [thread overview]
Message-ID: <4bzLd73KKxz2xG6@x86-01.haj.ipfire.org> (raw)
https://nightly.ipfire.org/next/2025-08-08%2015%3A10%3A39%20%2B0000-30cae58d/x86_64
commit 30cae58dd0be39699a95473e4abdbaace1d2f15f
Author: Michael Tremer <michael.tremer@ipfire.org>
Date: Fri Aug 8 15:10:39 2025 +0000
core198: Ship graphs.pl
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=30cae58dd0be39699a95473e4abdbaace1d2f15f
Full toolchain compilation
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:26: Building xz make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
xz-5.8.1.tar.xz checksum OK
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:26: Building yaml make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
yaml-0.2.5.tar.gz checksum OK
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:26: Building zabbix_agentd make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
zabbix-7.0.16.tar.gz checksum OK
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:27: Building zd1211-firmware make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
zd1211-firmware-1.5.tar.bz2 checksum OK
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:27: Building zerofree make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
zerofree-1.1.1.tgz checksum OK
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:27: Building zlib-ng make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
zlib-ng-2.2.4.tar.gz checksum OK
make: Leaving directory '/build/nightly/next/lfs'
Aug 9 00:00:27: Building zstd make: Entering directory '/build/nightly/next/lfs'
make: Nothing to be done for 'download'.
zstd-1.5.7.tar.gz checksum OK
make: Leaving directory '/build/nightly/next/lfs'
chroot: failed to run command ‘env’: No such file or directory
ERROR: Could not find GCC. You will need a working build enviroment in order to build the toolchain.[ FAIL ]
Check /build/nightly/next/log_x86_64/_build.preparation.log for errors if applicable[ FAIL ]
next reply other threads:[~2025-08-09 0:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 0:00 IPFire Nightly Builder [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-09 12:00 IPFire Nightly Builder
2025-08-09 11:00 IPFire Nightly Builder
2025-08-09 10:00 IPFire Nightly Builder
2025-08-09 9:00 IPFire Nightly Builder
2025-08-09 8:00 IPFire Nightly Builder
2025-08-09 7:00 IPFire Nightly Builder
2025-08-09 6:00 IPFire Nightly Builder
2025-08-09 5:00 IPFire Nightly Builder
2025-08-09 4:00 IPFire Nightly Builder
2025-08-09 3:00 IPFire Nightly Builder
2025-08-09 2:00 IPFire Nightly Builder
2025-08-09 1:00 IPFire Nightly Builder
2025-08-08 23:00 IPFire Nightly Builder
2025-08-08 22:00 IPFire Nightly Builder
2025-08-08 21:00 IPFire Nightly Builder
2025-08-08 20:00 IPFire Nightly Builder
2025-08-08 19:00 IPFire Nightly Builder
2025-08-08 18:06 IPFire Nightly Builder
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=4bzLd73KKxz2xG6@x86-01.haj.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