From: Nathan Rossi <nathan.rossi@xilinx.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [RFT] eglibc 2.19
Date: Mon, 10 Feb 2014 05:32:19 +0000 [thread overview]
Message-ID: <31681ec9-08a2-426e-b3d2-72f6c0d22073@AM1EHSMHS015.ehs.local> (raw)
In-Reply-To: <CAMKF1sptnVxCrjm7PAOCtRWzmSsxPv4nc0nUO82jMPQ+BCz9Hg@mail.gmail.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: Sunday, February 09, 2014 2:08 AM
> To: Patches and discussions about the oe-core layer; openembeded-devel;
> yocto@yoctoproject.org
> Subject: [OE-core] [RFT] eglibc 2.19
>
> Hi all
>
> I have staged a branch with eglibc 2.19 upgraded recipes here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-
> 2.19
>
> These are not final recipes there may be tweaks needed like adjusting
> SRC_URI
> later on.
>
> please help testing it out in your environments and machines
> I would be happy to help out with issues we find
Hi Khem,
I have given it a test with the machines on the meta-xilinx layer, specifically ARM Cortex A9 and MicroBlaze architectures. And there appears to be no issues.
Also I couldn't access your eglibc source tarball because of pesky corporate web filters, so I used a direct svn export of the upstream repo at the revision 25243, I assume there should be no differences?
On a side note, I haven't seen any mention of what is next regarding oe-core and eglibc. Since the eglibc project has closed its development (http://www.eglibc.org/archives/patches/msg01327.html), and that 2.19 is the final version. Are there any plans to switch oe-core to using glibc for the future? Just curious is all.
Regards,
Nathan
>
> Thank you
>
> -Khem
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Rossi <nathan.rossi@xilinx.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
openembeded-devel <Openembedded-devel@lists.openembedded.org>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFT] eglibc 2.19
Date: Mon, 10 Feb 2014 05:32:19 +0000 [thread overview]
Message-ID: <31681ec9-08a2-426e-b3d2-72f6c0d22073@AM1EHSMHS015.ehs.local> (raw)
In-Reply-To: <CAMKF1sptnVxCrjm7PAOCtRWzmSsxPv4nc0nUO82jMPQ+BCz9Hg@mail.gmail.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Khem Raj
> Sent: Sunday, February 09, 2014 2:08 AM
> To: Patches and discussions about the oe-core layer; openembeded-devel;
> yocto@yoctoproject.org
> Subject: [OE-core] [RFT] eglibc 2.19
>
> Hi all
>
> I have staged a branch with eglibc 2.19 upgraded recipes here
>
> http://git.openembedded.org/openembedded-core-contrib/log/?h=kraj/eglibc-
> 2.19
>
> These are not final recipes there may be tweaks needed like adjusting
> SRC_URI
> later on.
>
> please help testing it out in your environments and machines
> I would be happy to help out with issues we find
Hi Khem,
I have given it a test with the machines on the meta-xilinx layer, specifically ARM Cortex A9 and MicroBlaze architectures. And there appears to be no issues.
Also I couldn't access your eglibc source tarball because of pesky corporate web filters, so I used a direct svn export of the upstream repo at the revision 25243, I assume there should be no differences?
On a side note, I haven't seen any mention of what is next regarding oe-core and eglibc. Since the eglibc project has closed its development (http://www.eglibc.org/archives/patches/msg01327.html), and that 2.19 is the final version. Are there any plans to switch oe-core to using glibc for the future? Just curious is all.
Regards,
Nathan
>
> Thank you
>
> -Khem
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2014-02-10 5:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 16:08 [RFT] eglibc 2.19 Khem Raj
2014-02-10 5:32 ` Nathan Rossi [this message]
2014-02-10 5:32 ` Nathan Rossi
2014-02-10 7:31 ` [OE-core] " Khem Raj
2014-02-10 7:31 ` Khem Raj
2014-02-12 15:41 ` [OE-core] " Richard Purdie
2014-02-12 15:41 ` Richard Purdie
2014-02-12 16:53 ` [OE-core] " Richard Purdie
2014-02-12 16:53 ` Richard Purdie
2014-02-12 17:14 ` [OE-core] " Khem Raj
2014-02-12 17:14 ` Khem Raj
2014-02-12 18:20 ` [OE-core] " Khem Raj
2014-02-12 18:20 ` Khem Raj
2014-02-13 5:45 ` [OE-core] " Khem Raj
2014-02-13 5:45 ` Khem Raj
2014-02-17 15:25 ` [OE-core] " Richard Purdie
2014-02-17 15:25 ` Richard Purdie
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=31681ec9-08a2-426e-b3d2-72f6c0d22073@AM1EHSMHS015.ehs.local \
--to=nathan.rossi@xilinx.com \
--cc=Openembedded-devel@lists.openembedded.org \
--cc=openembedded-core@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.