From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: gcc 4.7 + mips64 architecture support
Date: Mon, 30 Apr 2012 16:39:53 +0100 [thread overview]
Message-ID: <1335800393.7415.26.camel@ted> (raw)
In-Reply-To: <CAMKF1sofwSqoCOeaLAb9fPZ7HMQH49OsCZ37wYLJkGz_doCkEw@mail.gmail.com>
On Mon, 2012-04-30 at 07:59 -0700, Khem Raj wrote:
> On Mon, Apr 30, 2012 at 7:53 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> >> hmmm. Whats the error ?
> >
> > http://autobuilder.yoctoproject.org:8010/builders/nightly-tiny/builds/42/steps/shell_24/logs/stdio
>
> that should not happen. Its seems to be issue in eglibc option group
> handling somehow its asking for regexp which should be isolated in
> option groups
>
> Did this work fine with 4.6 ?
Yes, it worked fine with 4.7 too. Only when we changed eglibc 2.13 ->
2.15 did it show up.
Cheers,
Richard
next prev parent reply other threads:[~2012-04-30 15:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-25 23:31 gcc 4.7 + mips64 architecture support Khem Raj
2012-04-26 14:47 ` Richard Purdie
2012-04-26 19:30 ` Richard Purdie
2012-04-26 21:06 ` Richard Purdie
2012-04-26 21:35 ` Khem Raj
2012-04-29 17:23 ` Khem Raj
2012-04-30 14:41 ` Richard Purdie
2012-04-30 14:47 ` Khem Raj
2012-04-30 14:53 ` Richard Purdie
2012-04-30 14:59 ` Khem Raj
2012-04-30 15:20 ` Mark Hatle
2012-04-30 15:39 ` Richard Purdie [this message]
2012-04-30 16:25 ` Khem Raj
2012-04-29 9:12 ` Martin Jansa
2012-04-29 15:36 ` Khem Raj
2012-04-30 11:07 ` Martin Jansa
2012-04-30 10:43 ` Martin Jansa
2012-04-30 14:15 ` Khem Raj
2012-04-30 14:31 ` Martin Jansa
2012-05-01 11:29 ` Martin Jansa
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=1335800393.7415.26.camel@ted \
--to=richard.purdie@linuxfoundation.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