All of lore.kernel.org
 help / color / mirror / Atom feed
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 21:25:41 +0000	[thread overview]
Message-ID: <1485293141.30673.63.camel@linuxfoundation.org> (raw)
In-Reply-To: <LOXP123MB011715CA6AFD7F2EA6C0964B85750@LOXP123MB0117.GBRP123.PROD.OUTLOOK.COM>

On Tue, 2017-01-24 at 18:08 +0000, Andrew Goodbody wrote:
> > 
> > From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> > I'm running out of time to write this up and post properly but the
> > patch I think should work is this:
> > 
> > http://git.yoctoproject.org/cgit.cgi/poky-contrib/commit/?h=rpurdie
> > /wip-
> > rss&id=414a75521f5d5dfb50385abab052f87dbc88f1c1
> > 
> > ("staging: Remove hardcoded PACKAGE_ARCHS from the class" in case I
> > rebase it)
> > 
> > I will get this cleaned up and sent soon.
> 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"?

Cheers,

Richard


  reply	other threads:[~2017-01-24 21:25 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 [this message]
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=1485293141.30673.63.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.