From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andrew Goodbody <andrew.goodbody@cambrionix.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: configure error for glibc 2.25.2
Date: Tue, 24 Jan 2017 17:02:51 +0000 [thread overview]
Message-ID: <1485277371.30673.59.camel@linuxfoundation.org> (raw)
In-Reply-To: <LOXP123MB0117B11AD747FFC1742D78C685750@LOXP123MB0117.GBRP123.PROD.OUTLOOK.COM>
On Tue, 2017-01-24 at 15:59 +0000, Andrew Goodbody wrote:
> Further to this I see the following message in
> log.do_prepare_recipe_sysroot.20511
>
> WARNING: Manifest /home/andrew/src/camol3/camol/build/tmp-camol-
> glibc/sstate-control/manifest-allarch-linux-libc-
> headers.populate_sysroot not found?
>
> Which is quite correct as that file does not exist, however the
> following file does exist
>
> /home/andrew/src/camol3/camol/build/tmp-camol-glibc/sstate-
> control/manifest-armv7at2hf-neon-linux-libc-headers.populate_sysroot
>
> So it looks like linux-libc-headers is not being installed in the
> recipe sysroot because it is looking for the manifest with the wrong
> arch.
>
> Anyone know what could be going wrong here?
Short answer is yes.
Your configuration is mixing different tune/package architectures and
is confusing recipe specific sysroots (armv7ahf-neon != armv7at2hf-
neon), looks like thumb and non-thumb.
I believe I have a patch which I'll send shortly as I've been chasing
this in other circumstances.
Cheers,
Richard
next prev parent reply other threads:[~2017-01-24 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 14:07 configure error for glibc 2.25.2 Andrew Goodbody
2017-01-24 14:42 ` Marko Lindqvist
2017-01-24 15:59 ` Andrew Goodbody
2017-01-24 17:02 ` Richard Purdie [this message]
2017-01-24 17:14 ` Andrew Goodbody
2017-01-24 17:50 ` Richard Purdie
2017-01-24 18:08 ` Andrew Goodbody
2017-01-24 21:25 ` Richard Purdie
2017-01-25 9:56 ` Andrew Goodbody
2017-01-25 10:04 ` Richard Purdie
2017-01-25 11:00 ` Andrew Goodbody
2017-01-25 11:03 ` Richard Purdie
2017-01-25 11:27 ` Andrew Goodbody
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=1485277371.30673.59.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=andrew.goodbody@cambrionix.com \
--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