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: Wed, 15 Aug 2018 21:09:19 +0200	[thread overview]
Message-ID: <87600bbg68.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180812170138.0b51be07@windsurf> (Thomas Petazzoni's message of "Sun, 12 Aug 2018 17:01:38 +0200")

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

 > Hello,
 > Today, I analyzed the defconfig build failures of
 > https://gitlab.com/buildroot.org/buildroot/pipelines/27617503. I fixed
 > a number of them, except two:

Thanks for doing that!

 >  - Problem of U-Boot failing to build due to a clash between the libfdt
 >    headers part of U-Boot, and the libfdt headers installed by our
 >    host-dtc package. We already made several changes in uboot.mk to try
 >    to fix this, but it still doesn't work properly.

 >    Does anybody has an idea ? Thomas DS, you already worked on this
 >    issue (you're the author of commit
 >    baae5156ce37e8b2775f04710f7d1c8e97e4114c). Any clue ?

 >    The problem is fixed in U-Boot 2018.01 but present in 2017.11.
 >    However, we have a number of vendor-provided U-Boot, and it's not
 >    necessarily easy to upgrade all defconfigs to use at least 2018.01.

Perhaps we could backport the changes and add as patches for the
affected defconfigs?

What is needed? Just the libfdt.h -> linux/libfdt.h you reported?

commit b08c8c4870831c9315dcae237772238e80035bd5
Author: Masahiro Yamada <yamada.masahiro@socionext.com>
Date:   Mon Mar 5 01:20:11 2018 +0900

    libfdt: move headers to <linux/libfdt.h> and <linux/libfdt_env.h>

    Thomas reported U-Boot failed to build host tools if libfdt-devel
    package is installed because tools include libfdt headers from
    /usr/include/ instead of using internal ones.


 >  - Problem of recent U-Boot that needs host-bison to build kconfig.
 >    Yann posted a patch series to make bison and flex hard requirements
 >    of Buildroot. Do we want to go this way ?

Sorry, I haven't looked at that series yet. If various packages start
needing this, and there aren't any version dependencies, then requiring
bison and flex is imho not a big problem (E.G. they are generally
available on all distributions).



 >    sheevaplug_defconfig
 >    https://gitlab.com/buildroot.org/buildroot/-/jobs/88314946

I still have this board somewhere. I'll take a look at bumping u-boot.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-08-15 19:09 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 [this message]
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
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=87600bbg68.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