From: IPFire Nightly Builder <nightly-builds@ipfire.org>
To: nightly-builds@lists.ipfire.org
Subject: [FAILED] Nightly Build of next (c77c537) for aarch64 on arm64-01.dub.ipfire.org
Date: Fri, 14 Aug 2020 17:04:03 +0000 [thread overview]
Message-ID: <4BSqXg5h9lz1xmv@arm64-01.dub.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2042 bytes --]
https://nightly.ipfire.org/next/2020-08-14%2015%3A16%3A57%20%2B0000-c77c5376/aarch64
commit c77c5376e458c2ae7ae0d54cae5d8f9ade2582ee
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Aug 14 15:16:57 2020 +0000
core149: add grub and install it at update
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=c77c5376e458c2ae7ae0d54cae5d8f9ade2582ee
Packaged toolchain compilation
Checking for necessary space on disk [ DONE ]
Building LFS
stage2 [ 0 ][ DONE ]
linux (4.14.184) KCFG=-headers [ 12 ][ DONE ]
man-pages (2.34) [ 4 ][ DONE ]
glibc (2.31) [ 4:15 ][ FAIL ]
yo_NG.UTF-8... done
yue_HK.UTF-8... done
yuw_PG.UTF-8... done
zh_CN.GB18030... done
zh_CN.GBK... done
zh_CN.UTF-8... done
zh_CN.GB2312... done
done
zh_HK.UTF-8...zh_HK.BIG5-HKSCS... done
zh_SG.UTF-8... done
zh_SG.GBK... done
zh_SG.GB2312... done
zh_TW.EUC-TW... done
zh_TW.UTF-8... done
done
zh_TW.BIG5zu_ZA.UTF-8...... done
zu_ZA.ISO-8859-1... done
done
done
done
done
make[3]: Leaving directory '/usr/src/glibc-2.31/localedata'
make[2]: Leaving directory '/usr/src/glibc-2.31'
make[1]: Leaving directory '/usr/src/glibc-build'
# Timezone data will be shipped by tzdata.
rm -rfv /usr/share/zoneinfo
removed directory '/usr/share/zoneinfo'
Updating linker cache...
Install done; saving file list to /usr/src/log/glibc-2.31 ...
ERROR: Building glibc [ FAIL ]
Check /build/nightly/next/log/_build.base.log for errors if applicable[ FAIL ]
reply other threads:[~2020-08-14 17:04 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=4BSqXg5h9lz1xmv@arm64-01.dub.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