From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2015-10-16
Date: Sat, 17 Oct 2015 11:57:54 +0200 [thread overview]
Message-ID: <87eggtzujh.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20151017063016.8F916101BB3@stock.ovh.net> (Thomas Petazzoni's message of "Sat, 17 Oct 2015 08:30:16 +0200 (CEST)")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Build statistics for 2015-10-16
> ===============================
> success : 196
> failures : 78
> timeouts : 0
> TOTAL : 274
> Classification of failures by reason
> ====================================
> busybox-1.24.0 | 14
Wow!
The problem seems to be that musl doesn't implement the wtmp stuff (and
stubs out the utmp functions):
http://lists.busybox.net/pipermail/busybox/2015-October/083447.html
Should we just disable wtmp and utmp suppert in our defconfig (which
means no last/who applets) or tweak the config when building with musl?
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2015-10-17 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-17 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-10-16 Thomas Petazzoni
2015-10-17 9:57 ` Peter Korsgaard [this message]
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=87eggtzujh.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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