From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mike Looijmans <mike.looijmans@topic.nl>,
openembedded-core@lists.openembedded.org
Subject: Re: How to avoid the poisoned sysroot?
Date: Sat, 19 Mar 2016 12:16:28 +0000 [thread overview]
Message-ID: <1458389788.7615.45.camel@linuxfoundation.org> (raw)
In-Reply-To: <56ED1FF4.7040901@topic.nl>
On Sat, 2016-03-19 at 10:46 +0100, Mike Looijmans wrote:
> After this commit:
>
> http://comments.gmane.org/gmane.comp.handhelds.openembedded.scm/81849
>
> some recipes fail with strange errors like:
> "fatal error: stdint.h: No such file or directory"
>
> What is wrong with the target recipe when this happens? What's
> expected
> of me?
It means that something is calling the cross compiler or linker but
losing our flags, particularly the --sysroot one. You need to ensure
the flags are getting passed in.
Cheers,
Richard
prev parent reply other threads:[~2016-03-19 12:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 9:46 How to avoid the poisoned sysroot? Mike Looijmans
2016-03-19 12:16 ` 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=1458389788.7615.45.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=mike.looijmans@topic.nl \
--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