From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-07
Date: Thu, 08 Mar 2018 08:56:27 +0100 [thread overview]
Message-ID: <87lgf3knkk.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180308070030.7B02A20993@mail.bootlin.com> (Thomas Petazzoni's message of "Thu, 8 Mar 2018 08:00:30 +0100 (CET)")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> Hello,
> Build statistics for 2018-03-07
> ===============================
> branch | OK | NOK | TIM | TOT |
> 2018.02.x | 11 | 1 | 0 | 12 |
> master | 141 | 56 | 0 | 197 |
> Results for branch '2018.02.x'
> ==============================
> Classification of failures by reason
> ------------------------------------
> cups-filters-1.17.9 | 1
> Detail of failures
> ------------------
> arc | cups-filters-1.17.9 | NOK | http://autobuild.buildroot.net/results/77a6369f3530a2a6a055f7fd664f1ad424274d77 |
The install steps are using ln -s -r, so we probably need a workaround
for old distributions like we have for systemd:
package/systemd/0002-install-don-t-use-ln-relative.patch
Olivier, can you take a look?
> Classification of failures by reason
> ------------------------------------
> zyre-1d949e4bf79b694ea883c3... | 14
Started happening when czmq got bumped, so probably an incompatibility
with the new version.
I see upstream released a v2.0.0 back in January 2017, so bumping the
version might fix it. Any takers?
> htop-2.1.0 | 10
It looks like it needs the same utf8 locale workaround as for
systemd. Any takers?
> ntp-4.2.8p11 | 7
Already fixed by 5766b6fb34a897092092f7d76d6b4f2bc8c48571
> liblo-0.29 | 6
musl compatibility issue:
In file included from server.c:54:0:
/home/buildroot/autobuild/run/instance-0/output/host/arm-buildroot-linux-musleabihf/sysroot/usr/include/sys/poll.h:1:2: error: #warning redirecting incorrect #include <sys/poll.h> to <poll.h> [-Werror=cpp]
#warning redirecting incorrect #include <sys/poll.h> to <poll.h>
It apparently builds with -Werror, which is why this is fatal.
Alex, you recently submitted a patch to pass --disable-werror, but the
configure script doesn't understand that option:
configure: WARNING: unrecognized options: --disable-gtk-doc, --disable-gtk-doc-html, --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --disable-nls, --disable-werror
Can you take another look? Thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2018-03-08 7:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-08 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-03-07 Thomas Petazzoni
2018-03-08 7:56 ` Peter Korsgaard [this message]
2018-03-08 7:57 ` Olivier Schonken
2018-03-08 8:20 ` Thomas Petazzoni
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=87lgf3knkk.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