From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2018-08-17
Date: Sat, 18 Aug 2018 22:56:04 +0200 [thread overview]
Message-ID: <20180818225604.23a0c55e@windsurf> (raw)
In-Reply-To: <CAFOYHZC34UUQvZ0rQWwsjMB-iCvWe7XLCR27LDgOMyzrRDZNhA@mail.gmail.com>
Hello,
On Sun, 19 Aug 2018 08:40:55 +1200, Chris Packham wrote:
> > Not sure what is going on here, but it happens only on Hollis autobuilder:
> >
> > http://autobuild.buildroot.net/?reason=micropython%
> >
> > Chris, perhaps you have an idea ?
>
> I've tried reproducing this a few times with no luck. Initially I thought
> it was due to a newer gcc generating new warnings, but then I tried gcc 8
> and didn't see any issue.
It happens only on Hollis autobuilder, which has the peculiarity of
running an older RHEL6.5 distro, providing a gcc 4.4 host compiler, and
general old tools.
So it is probably in this direction that we should search, even if the
problem apparently occurs when building code for the target.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-18 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-18 6:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-08-17 Thomas Petazzoni
2018-08-18 19:56 ` [Buildroot] Analysis of build " Thomas Petazzoni
2018-08-18 20:40 ` Chris Packham
2018-08-18 20:56 ` Thomas Petazzoni [this message]
2018-08-18 22:37 ` Peter Seiderer
2018-08-19 18:59 ` Peter Korsgaard
2018-08-19 19:26 ` 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=20180818225604.23a0c55e@windsurf \
--to=thomas.petazzoni@bootlin.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