From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-07
Date: Wed, 22 Aug 2018 10:30:42 +0200 [thread overview]
Message-ID: <20180822083042.GY15347@scaer> (raw)
In-Reply-To: <20180822072949.GX15347@scaer>
Baruch,All,
On 2018-08-22 09:29 +0200, Yann E. MORIN spake thusly:
> On 2018-08-09 07:08 +0300, Baruch Siach spake thusly:
> > Thomas Petazzoni writes:
> > > 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?
>
> For the records, I'm still investigating this issue, and I found that
> there is a delta in generated files, that cause the build issue.
>
> Now, the buildsystem for brltty is sufficiently inventive that it is not
> trivial to pinpoint why the generated files differ.
>
> I'll be pursuing my investigations...
Aha! I found it! Aha!
https://patchwork.ozlabs.org/patch/960852/
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-08-22 8:30 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
2018-08-22 7:29 ` Yann E. MORIN
2018-08-22 8:30 ` Yann E. MORIN [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=20180822083042.GY15347@scaer \
--to=yann.morin.1998@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.