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: Wed, 25 Jan 2017 10:04:15 +0000 [thread overview]
Message-ID: <1485338655.30673.73.camel@linuxfoundation.org> (raw)
In-Reply-To: <LOXP123MB0117D15626B7BF2AFE400B8A85740@LOXP123MB0117.GBRP123.PROD.OUTLOOK.COM>
On Wed, 2017-01-25 at 09:56 +0000, Andrew Goodbody wrote:
> >
> > From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> > On Tue, 2017-01-24 at 18:08 +0000, Andrew Goodbody wrote:
> > >
> > > Thanks but unfortunately that did not work for me.
> > >
> > > I did a cleanall on glibc before trying to build it, but the
> > > result
> > > was the same.
> > Try a "bitbake glibc-initial -c clean"?
> Sorry, it was glibc-initial that I ran the cleanall on, so just clean
> makes no difference.
Ok, what does bitbake -e show as the value of PACKAGE_EXTRA_ARCHS?
You could try putting something like:
bb.warn(d.expand("${SSTATE_MANIFESTS}/manifest-%s-*.populate_sysroot" % pkgarch))
into that 'for pkgarch in pkgarchs' loop and see what its looking for.
There is some detail I'm missing with the problem right now... :/
Cheers,
Richard
next prev parent reply other threads:[~2017-01-25 10:04 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
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 [this message]
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=1485338655.30673.73.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 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.