Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of defconfig build failures
Date: Mon, 27 Aug 2018 10:45:47 +0200	[thread overview]
Message-ID: <87efek9ozo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180827102815.23605ecd@windsurf> (Thomas Petazzoni's message of "Mon, 27 Aug 2018 10:28:15 +0200")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:

 > Hello,
 > On Mon, 27 Aug 2018 10:12:16 +0200, Peter Korsgaard wrote:

 >> > I.e. there is preprocessing of the dts file, then the actual
 >> > compilation via dtc.
 >> > With this in mind, I actually don't think that this behavior is
 >> > negatively impacted by my changes. I now think it is a failure on top
 >> > of the original failures. When I undo my changes prior to running this
 >> > command, then the same errors occur. And since no other binary than
 >> > the compiler (preprocessor) and the prebuilt dtc is used, there cannot
 >> > be other impact of the changes I did to two header files.  
 >> 
 >> > Nevertheless, this defconfig still does not build correctly.  
 >> 
 >> :/
 >> 
 >> I guess giving the timing, the best solution for 2018.08 is to simply
 >> revert the dtc bump?

 > Is this fixing all issues we have, without introducing other problems ?
 > If so, then I'm fine with a revert of the dtc bump, of course.

That was my understanding based on Yann's git bisect, yes. These
defconfigs all used to work.

Yann?

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-08-27  8:45 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
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 [this message]
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=87efek9ozo.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