From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Linaro Dev <linaro-dev@lists.linaro.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: OE gcc-cross with builtin sysroot, BUG?
Date: Wed, 11 Sep 2013 14:06:20 +0100 [thread overview]
Message-ID: <1378904780.3484.183.camel@ted> (raw)
In-Reply-To: <CAP71Wjw7-7FX39-baCq+opPry1rpV9UqNDjX8MZRrJ6+qAKtSw@mail.gmail.com>
On Wed, 2013-09-11 at 15:01 +0200, Nicolas Dechesne wrote:
>
> On Wed, Sep 11, 2013 at 2:00 PM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> Not really, its actually intentionally designed like this
> since its
> pointless rebuilding gcc-cross multiple time just because we
> want to use
> it with a different sysroot. We therefore just pass in the
> arguments to
> the compiler to ensure it uses the right one. If you remove
> them, you
> hit the problems you describe.
>
> We should probably compile in a bogus sysroot so it never
> works and
> makes this kind of issue more visible.
>
> hmm. ok. i see. it would certainly help to have a better 'error'
> message... i suppose that not having a builtin sysroot at all, would
> be an even bigger problem as it would default to /usr/include...
>
>
Right, that would be even worse than a poisoned one...
Cheers,
Richard
>
prev parent reply other threads:[~2013-09-11 13:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 10:29 OE gcc-cross with builtin sysroot, BUG? Nicolas Dechesne
2013-09-11 11:33 ` Tomas Frydrych
2013-09-11 12:03 ` Richard Purdie
2013-09-11 12:00 ` Richard Purdie
2013-09-11 13:01 ` Nicolas Dechesne
2013-09-11 13:06 ` Richard Purdie [this message]
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=1378904780.3484.183.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=linaro-dev@lists.linaro.org \
--cc=nicolas.dechesne@linaro.org \
--cc=openembedded-core@lists.openembedded.org \
/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