Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I.
Date: Thu, 4 Aug 2016 21:32:23 -0700	[thread overview]
Message-ID: <7deac099-e349-64cc-3c20-02f0c615bf38@gmail.com> (raw)
In-Reply-To: <005f01d1ea72$b4b24b90$1e16e2b0$@bbn.com>



On 7/30/16 7:57 AM, David Raeman wrote:
> Yann, All,
> 
> On Fri, Jul 29, 2016 at 5:16 PM, Yann E. MORIN wrote:
>> U-Boot or Qemu? I thought you needed that for your custom Qemu
> 
> The problem was revealed when I added a br2-external package for 
> custom Qemu, but I traced the root issue to be with u-boot and how it
> is impacted by the include directory added by HOST_CPPFLAGS.
> 
> The custom Qemu required me to install libfdt into the host area -
> nothing wrong with doing that.  But having libfdt installed in
> HOST_DIR causes u-boot to fail, because u-boot was finding libfdt.h 
> in HOST_DIR/usr/include prior to searching its own directory for its
> local modified copy of that same filename.

I think thats a problem in u-boot's build system. So its better to
address it there.

> 
>> And thus we should revert that patch. Will you send a patch to do the revert,
>> please?
> 
> Yes I will.  I believe the patch to revert should also back out patch 
> 2/2 that installed libfdt to HOST_DIR as a part of host-dtc.  As 
> mentioned above, if you keep that change and only revert the change to
> HOST_CPPFLAGS, then u-boot to fail unless something else is done.  Do
> you agree I should revert both changes with this new patch, to ensure
> there is no leftover breakage?
> 
>> So, I think the best solution would be for U-Boot^WQemu to rename their
>> header.
> 
> Given the various considerations, I agree this is the lowest-risk
> solution.  Keeping in mind that any other package with a local header
> file in conflict with a HOST_DIR header file can experience this same
> problem.  The root issue is that usage of CPPFLAGS causes packages
> to search HOST_DIR/usr/include before they search their local source
> directories.
> 
> I may be a bit of time before I can submit a new patch to rename the
> header file within u-boot.
> 
> Cheers,
> David
> 
> 

  reply	other threads:[~2016-08-05  4:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25 19:52 [Buildroot] [PATCH 1/2] package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I David Raeman
2016-07-25 19:52 ` [Buildroot] [PATCH 2/2] host-dtc: Install libftd and associated header files David Raeman
2016-07-25 20:01   ` Thomas Petazzoni
2016-07-25 20:26     ` David Raeman
2016-07-25 21:39       ` Yann E. MORIN
2016-07-25 21:52 ` [Buildroot] [PATCH 1/2] package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I Yann E. MORIN
2016-07-25 21:57 ` Thomas Petazzoni
2016-07-28 22:00 ` Yann E. MORIN
2016-07-28 22:04   ` Khem Raj
2016-07-29  7:32     ` Thomas Petazzoni
2016-07-29  8:16       ` Khem Raj
2016-07-29  9:23         ` Thomas Petazzoni
2016-07-29 15:08           ` Khem Raj
2016-07-29 19:35             ` David Raeman
2016-07-29 21:15               ` Yann E. MORIN
2016-07-30 14:57                 ` David Raeman
2016-08-05  4:32                   ` Khem Raj [this message]
2016-08-05  4:30               ` Khem Raj
2016-08-02 21:39     ` Thomas Petazzoni
2016-07-29  0:09   ` David Raeman
2016-07-29  4:18   ` [Buildroot] [PATCH 1/1] host-python: Find headers provided by -isystem flag in CPPFLAGS David Raeman
2016-08-01 21:59 ` [Buildroot] [PATCH 1/2] package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I Yann E. MORIN
2016-08-01 22:19   ` Yann E. MORIN
2016-08-02 12:21   ` David Raeman

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=7deac099-e349-64cc-3c20-02f0c615bf38@gmail.com \
    --to=raj.khem@gmail.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