From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>
Subject: Re: Upcoming Yocto 1.2.1 "denzil" release this week.
Date: Wed, 11 Jul 2012 13:36:48 -0700 [thread overview]
Message-ID: <4FFDE3E0.2040900@linux.intel.com> (raw)
In-Reply-To: <1342032628.11939.37.camel@ted>
On 07/11/2012 11:50 AM, Richard Purdie wrote:
> On Wed, 2012-07-11 at 19:00 +0100, Paul Eggleton wrote:
>> On Wednesday 11 July 2012 17:55:18 McClintock Matthew-B29882 wrote:
>>> On Wed, Jul 11, 2012 at 6:00 AM, Richard Purdie
>>> <richard.purdie@linuxfoundation.org> wrote:
>>>> On Wed, 2012-07-11 at 09:57 +0100, Jack Mitchell wrote:
>>>>> Are Khems eglibc patches going to make it in for this - 2.16 is playing
>>>>> havoc with my builds at the moment and surely will with everyone else
>>>>> when the major distros catch up.
>>>>
>>>> Its too late to get those pieces into 1.2.1, they're not even in master
>>>> yet, let alone in a stable release branch.
>>>>
>>>> I'm proposing we get 1.2.1 out, get the 2.16 pieces tested in master,
>>>> then port them to the denzil branch quickly post release so they'd make
>>>> any 1.2.2 release and are available on the git branch for people using
>>>> the stable branch.
>>>
>>> Can you fill me in? Why would a point release include such a dramatic
>>> upgrade?
>>
>> I think what we would be looking at would be just adding the fixes to allow the
>> native packages to build against eglibc 2.16 so it can work on host distros
>> that use it, not bringing eglibc 2.16 itself in for the target.
>
> Right, this would just be to allow edison to work on systems that have a
> native eglibc 2.16. I'm not convinced we have the patches worked out yet
> though. Target eglibc would remain with whatever is in edison (2.13?).
>
I assume you mean denzil, not edison, or do we also need to be planning
a 1.1.3?
Sau!
> Cheers,
>
> Richard
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
next prev parent reply other threads:[~2012-07-11 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-11 4:42 Upcoming Yocto 1.2.1 "denzil" release this week Scott Garman
2012-07-11 8:57 ` Jack Mitchell
2012-07-11 11:00 ` Richard Purdie
2012-07-11 17:55 ` McClintock Matthew-B29882
2012-07-11 18:00 ` Paul Eggleton
2012-07-11 18:50 ` Richard Purdie
2012-07-11 20:36 ` Saul Wold [this message]
2012-07-11 20:43 ` McClintock Matthew-B29882
2012-07-12 17:13 ` Zhang, Jessica
2012-07-12 20:37 ` McClintock Matthew-B29882
2012-07-11 21:10 ` 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=4FFDE3E0.2040900@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=B29882@freescale.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox