From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (1c64d20) for riscv64 on riscv64-01.haj.ipfire.org
Date: Tue, 27 Aug 2024 13:06:23 +0000 [thread overview]
Message-ID: <4WtSV75yBWz30Gf@riscv64-01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 4019 bytes --]
https://nightly.ipfire.org/next/2024-08-27%2009%3A49%3A09%20%2B0000-1c64d207/riscv64
commit 1c64d2071382093a5d87e875e34850cf071bc292
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Tue Aug 27 09:49:09 2024 +0000
core189: Ship OpenSSL
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=1c64d2071382093a5d87e875e34850cf071bc292
Packaged toolchain compilation
Building IPFire
stage2 [ 25 ][ DONE ]
linux (6.6.47) HEADERS=1 [ 9:00 ][ DONE ]
man-pages (6.9.1) [ 3:42 ][ DONE ]
glibc (2.40) [ 42:37 ][ DONE ]
tzdata (2024a) [ 1:21 ][ DONE ]
cleanup-toolchain [ 2 ][ DONE ]
zlib (1.3.1) [ 31 ][ DONE ]
gcc (14.2.0) PASS=A [ 4:43 ][ DONE ]
zstd (1.5.6) [ 42 ][ DONE ]
autoconf (2.71) [ 30 ][ DONE ]
autoconf-archive (2023.02.20) [ 38 ][ DONE ]
automake (1.17) [ 59 ][ DONE ]
help2man (1.49.3) [ 19 ][ DONE ]
libtool (2.4.7) [ 2:49 ][ DONE ]
binutils (2.43) [ 23:34 ][ DONE ]
gmp (6.3.0) [ 8:41 ][ DONE ]
mpfr (4.2.1) [ 4:44 ][ DONE ]
libmpc (1.3.1) [ 2:04 ][ DONE ]
libxcrypt (4.4.36) [ 3:46 ][ DONE ]
file (5.45) [ 3:16 ][ DONE ]
gcc (14.2.0) [ 1:11:23 ][ FAIL ]
rm -f /usr/bin/c++; \
( cd /usr/bin && \
ln g++ c++ ); \
if [ -f cc1plus ] ; then \
if [ ! -f g++-cross ] ; then \
rm -f /usr/bin/riscv64-unknown-linux-gnu-g++; \
( cd /usr/bin && \
ln g++ riscv64-unknown-linux-gnu-g++ ); \
rm -f /usr/bin/riscv64-unknown-linux-gnu-c++; \
( cd /usr/bin && \
ln c++ riscv64-unknown-linux-gnu-c++ ); \
fi ; \
fi; \
fi
/tools_riscv64/bin/install -c lto-dump \
/usr/bin/lto-dump
for file in gnat1 cc1 cc1plus d21 f951 go1 lto1 cc1gm2 cc1obj cc1objplus crab1; do \
if [ -f $file ] ; then \
rm -f /usr/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/$file; \
/tools_riscv64/bin/install -c $file /usr/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/$file; \
else true; \
fi; \
done
/tools_riscv64/bin/install: error copying 'cc1' to '/usr/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/cc1': No space left on device
/tools_riscv64/bin/install: error copying 'cc1plus' to '/usr/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/cc1plus': No space left on device
/tools_riscv64/bin/install: error copying 'lto1' to '/usr/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/lto1': No space left on device
for file in collect2 ..; do \
if [ x"$file" != x.. ]; then \
rm -f /usr/lib/gcc/riscv64-unknown-linux-gnu/14.2.0/$file; \
/tools_riscv64/bin/ins
ERROR: Building gcc [ FAIL ]
Check /build/nightly/next/log_riscv64/_build.ipfire.log for errors if applicable[ FAIL ]
reply other threads:[~2024-08-27 13:06 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=4WtSV75yBWz30Gf@riscv64-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