From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-07
Date: Thu, 09 Aug 2018 07:08:01 +0300 [thread overview]
Message-ID: <87mutwb2se.fsf@tkos.co.il> (raw)
In-Reply-To: <20180808060047.9CC13209AD@mail.bootlin.com>
Hi Thomas, Yann, Romain, Richard,
Thomas Petazzoni writes:
> Results for branch '2018.05.x'
> ==============================
>
> Classification of failures by reason
> ------------------------------------
>
> host-libglib2-2.56.1 | 1
>
> Detail of failures
> ------------------
>
> arm | host-libglib2-2.56.1 | NOK | http://autobuild.buildroot.net/results/ba24c2754923580bac4c1d9e6ecf8251735ae65f |
Backport of bb3f944d6669dbf from master would fix this one.
> Results for branch 'master'
> ===========================
>
> xtensa | brltty-5.5 | NOK | http://autobuild.buildroot.net/results/55b271cceb5b749f911266ed96998c4ee730fb86 |
> sh4 | brltty-5.5 | NOK | http://autobuild.buildroot.net/results/f8ff8c24d940113d7eb9729ae0b1b8e454cb4523 |
> mips64el | brltty-5.5 | NOK | http://autobuild.buildroot.net/results/c1829952aec2356905a2d5559d77b3e79739ea21 |
I could not reproduce this one here. The autobuilder indicates that it
only happens on the autobuilders of Yann, Romain and Richard:
http://autobuild.buildroot.net/?reason=brltty-5.5
It looks like ATSPI2_INCLUDES and GLIB2_INCLUDES evaluate to empty
strings in Drivers/Screen/AtSpi2/Makefile.in on these
builders. config.log looks normal though.
Maybe one of you can take a look?
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2018-08-09 4:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-07 Thomas Petazzoni
2018-08-09 4:08 ` Baruch Siach [this message]
2018-08-22 7:29 ` Yann E. MORIN
2018-08-22 8:30 ` Yann E. MORIN
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=87mutwb2se.fsf@tkos.co.il \
--to=baruch@tkos.co.il \
--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