From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] uclibc and related fixes
Date: Wed, 22 Jun 2011 16:42:17 +0100 [thread overview]
Message-ID: <1308757337.20015.72.camel@rex> (raw)
In-Reply-To: <cover.1308706511.git.raj.khem@gmail.com>
On Tue, 2011-06-21 at 18:44 -0700, Khem Raj wrote:
> Fix uclibc build for x86_64
> gettext compile failed on uclibc so fix it and additionally
> remove unused patches
> Add required support for systemd to function with uclibc
> Quash a parse warning where uclibc-initial and uclibc
> both provided libsegfault
>
> The following changes since commit 78de64f58b98101f5be5778e9ecbdaae5ba32997:
>
> binutils_2.21.bb: Fix ld segfault exposed by eglibc 2.14 on x86_64 (2011-06-21 17:58:06 -0700)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib kraj/uclibc
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/uclibc
>
> Khem Raj (4):
> uclibc.inc: libsegfault is only RPROVIDED by uclibc
> gettext-0.18.1.1: Remove unused patches
> uclibc/x86_64/uClibc.machine: Enable ARCH_USE_MMU
> uclibc: Add support for $ORIGIN
Merged to master, thanks.
I had reservations about the first one as hardcoding PN can have issues
with BBCLASSEXTEND but looking at the recipe, there are bigger issues if
we were ever to do that :/
Cheers,
Richard
next prev parent reply other threads:[~2011-06-22 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 1:44 [PATCH 0/4] uclibc and related fixes Khem Raj
2011-06-22 1:44 ` [PATCH 1/4] uclibc.inc: libsegfault is only RPROVIDED by uclibc Khem Raj
2011-06-22 1:44 ` [PATCH 2/4] gettext-0.18.1.1: Remove unused patches Khem Raj
2011-06-22 1:44 ` [PATCH 3/4] uclibc/x86_64/uClibc.machine: Enable ARCH_USE_MMU Khem Raj
2011-06-22 1:44 ` [PATCH 4/4] uclibc: Add support for $ORIGIN Khem Raj
2011-06-22 15:42 ` Richard Purdie [this message]
2011-06-22 15:57 ` [PATCH 0/4] uclibc and related fixes Khem Raj
2011-06-22 16:10 ` 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=1308757337.20015.72.camel@rex \
--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 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.