From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: solidrun_macchiatobin_marvell: fix u-boot build
Date: Thu, 16 Aug 2018 22:00:45 +0200 [thread overview]
Message-ID: <20180816220045.0a74a6af@windsurf> (raw)
In-Reply-To: <bc4ad6ef454508016634b1074fe83681946f4826.1534422853.git.baruch@tkos.co.il>
Hello,
On Thu, 16 Aug 2018 15:34:13 +0300, Baruch Siach wrote:
> U-Boot local libfdt headers conflict with host-dtc provided headers.
> Disable host-dtc, and backport two upstream U-Boot patches to fix build
> without external libfdt headers.
>
> U-Boot build still fail when the host provides its own libfdt header
> (e.g., Debian libfdt-dev package), or when BR2_PACKAGE_HOST_DTC is
> enabled. Fixing that seems to require much more involved code changes.
> Fix the common case for now.
>
> Fixes partially:
> https://gitlab.com/buildroot.org/buildroot/-/jobs/88314956
>
> Cc: Sergey Matyukevich <geomatsi@gmail.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
This issue is happening for 30-40 defconfigs. I don't think adding a
4500 lines patch for each defconfig is really the right solution,
especially because it also doesn't fix the situation of someone
building U-Boot outside of a pre-existing defconfig.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-16 20:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 12:34 [Buildroot] [PATCH] configs: solidrun_macchiatobin_marvell: fix u-boot build Baruch Siach
2018-08-16 20:00 ` Thomas Petazzoni [this message]
2018-08-21 22:24 ` Arnout Vandecappelle
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=20180816220045.0a74a6af@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 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.