From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I.
Date: Mon, 1 Aug 2016 23:59:09 +0200 [thread overview]
Message-ID: <20160801215909.GA5990@free.fr> (raw)
In-Reply-To: <20160725195227.21112-1-draeman@bbn.com>
David, All,
On 2016-07-25 15:52 -0400, David Raeman spake thusly:
> HOST_CFLAGS includes a search path for HOST_DIR/usr/include using -I. When
> HOST_CFLAGS is used by a package, these flags are passed to the compiler ahead
> of flags passed by the package's internal make system. If a package has a
> header file with the same name as a header file in HOST_DIR, this causes the
> toolchain to prefer the file from the system include directory because its -I
> appears first on the command line. I believe conflicts should prefer the file
> provided by the package. This can be accomplished by using -isystem, which is
> more appropriate then -I for system-level include paths.
[--SNIP--]
In fact, this does not work, and the patch was reverted (for background).
What we need is that gcc follows the following sequence when looking for
headers:
1- search paths specified with -I by the package
2- search our $(HOST_DIR)/usr/include
3- search the host system /usr/include
However, I can't find anything in the gcc manpage that allows to add the
search path we need in (2).
All I can see is -idirafter, to add search paths after all other
non-system and system paths.
So, probably the following would not be very far from what we'd have to
do:
-nostdinc -idirafter $(HOST_DIR)/usr/include -idirafter /usr/include
This tells gcc to not look at the system include path, so it is left
with only the paths specified by the package, and then as a fallback,
out $(HOST_DIR)/usr/include, and then as a last resort, the host-system
/usr/include dirs, since the last two are -idirafter:
-idirafter dir
Search dir for header files, but do it after all directories
specified with -I and the standard system directories have
been exhausted. dir is treated as a system include directory.
Thoughts?
David, would you care to see if:
1- it fixes your own problem?
2- it fixes the python issues we've had with -isystem?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2016-08-01 21:59 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
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 ` Yann E. MORIN [this message]
2016-08-01 22:19 ` [Buildroot] [PATCH 1/2] package/Makefile.in should grab HOST_DIR headers using -isystem instead of -I 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=20160801215909.GA5990@free.fr \
--to=yann.morin.1998@free.fr \
--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.