From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org \(yocto@yoctoproject.org\)"
<yocto@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<Openembedded-core@lists.openembedded.org>
Subject: Re: eglibc (would be 2.18) recipes
Date: Thu, 27 Jun 2013 08:20:15 +0100 [thread overview]
Message-ID: <1372317615.9930.180.camel@ted> (raw)
In-Reply-To: <1831F7C6-54BC-4E5F-BC00-1B8C17E8D1FD@gmail.com>
On Wed, 2013-06-26 at 14:06 -0700, Khem Raj wrote:
> Hi All
>
> I have put together eglibc recipes for upcoming 2.18 release and pushed to a contrib tree here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.18
>
> They built angstrom/systemd-images fine and booted OK on all supported qemu machines
> on OE-Core
>
> Please test them out in your configurations and machines and provide feedback, lets weed out
> the issue early
You have a fix for bug 4168 in there that nobody else can reproduce or
understand:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4168
I'd really like to better understand what is happening there before we
pull that one in.
Cheers,
Richard
WARNING: multiple messages have this Message-ID (diff)
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org \(yocto@yoctoproject.org\)"
<yocto@yoctoproject.org>,
"openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<Openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] eglibc (would be 2.18) recipes
Date: Thu, 27 Jun 2013 08:20:15 +0100 [thread overview]
Message-ID: <1372317615.9930.180.camel@ted> (raw)
In-Reply-To: <1831F7C6-54BC-4E5F-BC00-1B8C17E8D1FD@gmail.com>
On Wed, 2013-06-26 at 14:06 -0700, Khem Raj wrote:
> Hi All
>
> I have put together eglibc recipes for upcoming 2.18 release and pushed to a contrib tree here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-2.18
>
> They built angstrom/systemd-images fine and booted OK on all supported qemu machines
> on OE-Core
>
> Please test them out in your configurations and machines and provide feedback, lets weed out
> the issue early
You have a fix for bug 4168 in there that nobody else can reproduce or
understand:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4168
I'd really like to better understand what is happening there before we
pull that one in.
Cheers,
Richard
next prev parent reply other threads:[~2013-06-27 7:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 21:06 eglibc (would be 2.18) recipes Khem Raj
2013-06-27 1:46 ` Otavio Salvador
2013-06-27 1:46 ` [OE-core] " Otavio Salvador
2013-06-27 2:49 ` Khem Raj
2013-06-27 2:49 ` [OE-core] " Khem Raj
2013-06-27 7:20 ` Richard Purdie [this message]
2013-06-27 7:20 ` Richard Purdie
2013-06-27 15:10 ` Khem Raj
2013-06-27 15:10 ` [OE-core] " Khem Raj
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=1372317615.9930.180.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=yocto@yoctoproject.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.