From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] toolchain/wrapper: extend paranoid check to -isystem
Date: Wed, 24 Aug 2016 16:12:24 +0200 [thread overview]
Message-ID: <20160824141224.GA5730@free.fr> (raw)
In-Reply-To: <4a80aa4c-4bbf-55ca-e310-2c4e1dcad3c4@mind.be>
Arnout, All,
On 2016-08-24 03:18 +0200, Arnout Vandecappelle spake thusly:
> On 17-08-16 16:42, Yann E. MORIN wrote:
> > Some packages, like libbsd, use -isystem flags to provide so-called
> > overrides to the system include files. In this particular case, this
> > is used in a .pc file, then used by antoher package; pkgconf does not
> > mangle this path; and eventually that other package ends up using
> > /usr/include/bsd to search for headers.
> >
> > Our current toolchain wrapper is limited to looking fo -I and -L, so
> > the paranoid check does not kick in.
> >
> > Extend the paranoid check to also look for the -isystem option.
>
> While we're at it: -idirafter, -iprefix, -iwithprefix, -iwithprefixbefore,
> -isysroot, -imultilib, -iquote.
Did you meant we should handle all of them now? Are were you listing
them for the future, when we encoutner issues with any if them?
> And then there is -B, but if someone passes that, it's really broken :-) And
> --sysroot, also interesting if that is passed. But I guess these things are
> going a bit too far.
--sysroot is even more fun, as it can be written: --sysroot=dir , so
we'd need to take care of this as well...
Lotta fun in sight! ;-)
> > Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > Cc: Arnout Vandecappelle <arnout@mind.be>
> > ---
> > toolchain/toolchain-wrapper.c | 18 ++++++++++--------
> > 1 file changed, 10 insertions(+), 8 deletions(-)
> >
> > diff --git a/toolchain/toolchain-wrapper.c b/toolchain/toolchain-wrapper.c
> > index b8b3cbe..8a9c3b3 100644
> > --- a/toolchain/toolchain-wrapper.c
> > +++ b/toolchain/toolchain-wrapper.c
> > @@ -241,17 +241,19 @@ int main(int argc, char **argv)
> > /* Check for unsafe library and header paths */
> > for (i = 1; i < argc; i++) {
> >
> > - /* Skip options that do not start with -I and -L */
> > - if (strncmp(argv[i], "-I", 2) && strncmp(argv[i], "-L", 2))
> > + /* Skip options that do not start with -I, -isystem or -L */
> > + if ( strncmp(argv[i], "-I", 2)
> > + && strncmp(argv[i], "-L", 2)
> > + && strcmp(argv[i], "-isystem"))
> > continue;
> >
> > - /* We handle two cases: first the case where -I/-L and
> > - * the path are separated by one space and therefore
> > - * visible as two separate options, and then the case
> > - * where they are stuck together forming one single
> > - * option.
> > + /* We handle two cases: first the case where -I/-L/-isystem
> > + * and the path are separated by one space and therefore
> > + * visible as two separate options, and then the case where
> > + * they are stuck together forming one single option.
> > + * -isystem is necessarily in the first case.
>
> Unfortunately, that's not true. You can pass something like -isystemfoo and it
> will add ./foo to the search path. Ain't gcc fun... I'll leave it as an exercise
> to the reader to handle that case :-P
I think we should not care too much about this, should we? In the end,
this would not be an unsafe path...
But I think my next iteration should cover all your comments (as well as
on the previous patch).
Thanks! ;-)
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-24 14:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-17 14:42 [Buildroot] [PATCH 1/2] toolchain/wrapper: display options leading to a paranoid failure Yann E. MORIN
2016-08-17 14:42 ` [Buildroot] [PATCH 2/2] toolchain/wrapper: extend paranoid check to -isystem Yann E. MORIN
2016-08-24 1:18 ` Arnout Vandecappelle
2016-08-24 14:12 ` Yann E. MORIN [this message]
2016-08-24 15:23 ` Arnout Vandecappelle
2016-08-24 1:09 ` [Buildroot] [PATCH 1/2] toolchain/wrapper: display options leading to a paranoid failure Arnout Vandecappelle
-- strict thread matches above, loose matches on Subject: below --
2016-08-24 14:19 Yann E. MORIN
2016-08-24 14:19 ` [Buildroot] [PATCH 2/2] toolchain/wrapper: extend paranoid check to -isystem Yann E. MORIN
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=20160824141224.GA5730@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.