From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of defconfig build failures
Date: Thu, 16 Aug 2018 00:18:29 +0200 [thread overview]
Message-ID: <20180816001829.3f7a1436@windsurf> (raw)
In-Reply-To: <87ftzf9v7u.fsf@dell.be.48ers.dk>
Hello,
On Wed, 15 Aug 2018 23:27:17 +0200, Peter Korsgaard wrote:
> >> Perhaps we could backport the changes and add as patches for the
> >> affected defconfigs?
>
> > The problem is that it will still affect anyone doing a U-Boot build,
> > outside of the defconfigs.
>
> Ok. Is this a new failure introduced by something we do
> wrong/differently in Buildroot, or just something that is broken by
> building with newer compilers?
I don't think it's related to building with new compilers. It's just
some U-Boot versions that are broken if libfdt headers are already
available in the include path.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-15 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-12 15:01 [Buildroot] Analysis of defconfig build failures Thomas Petazzoni
2018-08-15 19:09 ` Peter Korsgaard
2018-08-15 19:34 ` Thomas Petazzoni
2018-08-15 21:27 ` Peter Korsgaard
2018-08-15 22:18 ` Thomas Petazzoni [this message]
2018-08-16 19:52 ` Thomas De Schampheleire
2018-08-16 20:06 ` Thomas Petazzoni
2018-08-23 19:49 ` Thomas De Schampheleire
2018-08-25 20:21 ` Thomas De Schampheleire
2018-08-25 20:54 ` Thomas De Schampheleire
2018-08-27 8:12 ` Peter Korsgaard
2018-08-27 8:28 ` Thomas Petazzoni
2018-08-27 8:45 ` Peter Korsgaard
2018-08-27 21:01 ` Thomas De Schampheleire
2018-08-27 21:19 ` Peter Korsgaard
2018-08-28 8:07 ` Luca Ceresoli
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=20180816001829.3f7a1436@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