From: Khem Raj <raj.khem@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
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: Wed, 26 Jun 2013 19:49:10 -0700 [thread overview]
Message-ID: <51CBA826.3070701@gmail.com> (raw)
In-Reply-To: <CAP9ODKqVqLxQ8QNY_1DDJGjRSrW=6YsiHdwPjpzE9EKmybQ4+Q@mail.gmail.com>
On 06/26/2013 06:46 PM, Otavio Salvador wrote:
> On Wed, Jun 26, 2013 at 6:06 PM, Khem Raj <raj.khem@gmail.com> 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
>
> Could you also make a tree based on poky?
the patches should apply on top of poky as it is.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>
WARNING: multiple messages have this Message-ID (diff)
From: Khem Raj <raj.khem@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
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: Wed, 26 Jun 2013 19:49:10 -0700 [thread overview]
Message-ID: <51CBA826.3070701@gmail.com> (raw)
In-Reply-To: <CAP9ODKqVqLxQ8QNY_1DDJGjRSrW=6YsiHdwPjpzE9EKmybQ4+Q@mail.gmail.com>
On 06/26/2013 06:46 PM, Otavio Salvador wrote:
> On Wed, Jun 26, 2013 at 6:06 PM, Khem Raj <raj.khem@gmail.com> 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
>
> Could you also make a tree based on poky?
the patches should apply on top of poky as it is.
>
> --
> Otavio Salvador O.S. Systems
> http://www.ossystems.com.br http://projetos.ossystems.com.br
> Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
>
next prev parent reply other threads:[~2013-06-27 2:49 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 [this message]
2013-06-27 2:49 ` Khem Raj
2013-06-27 7:20 ` Richard Purdie
2013-06-27 7:20 ` [OE-core] " 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=51CBA826.3070701@gmail.com \
--to=raj.khem@gmail.com \
--cc=Openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
--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.