From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] glibc_2.9.bb : add already existing OE patch arm-lowlevellock-include-tls.patch
Date: Wed, 30 Sep 2009 06:59:28 -0400 [thread overview]
Message-ID: <4AC33A10.2040707@balister.org> (raw)
In-Reply-To: <1254297499-3508-2-git-send-email-dp@xora.org.uk>
[-- Attachment #1: Type: text/plain, Size: 948 bytes --]
Acked-by: Philip Balister <philip@balister.org>
On 09/30/2009 03:58 AM, Graeme Gregory wrote:
> This is required to get glibc 2.9 to build on arm oabi. eglibc already
> includes this patch and the patch is already in OE
>
> Signed-off-by: Graeme Gregory<dp@xora.org.uk>
> ---
> recipes/glibc/glibc_2.9.bb | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/recipes/glibc/glibc_2.9.bb b/recipes/glibc/glibc_2.9.bb
> index c3ebc16..56a6ff8 100644
> --- a/recipes/glibc/glibc_2.9.bb
> +++ b/recipes/glibc/glibc_2.9.bb
> @@ -64,6 +64,7 @@ SRC_URI = "ftp://ftp.gnu.org/pub/gnu/glibc/glibc-${PV}.tar.bz2 \
> file://march-i686.patch;patch=1;pnum=0 \
> file://tls_i486.patch;patch=1 \
> file://glibc-2.9-use-_begin.patch;patch=1 \
> + file://arm-lowlevellock-include-tls.patch;patch=1 \
> "
>
> # Build fails on sh3 and sh4 without additional patches
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3316 bytes --]
next prev parent reply other threads:[~2009-09-30 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-30 7:58 Signoff needed from dev on core glibc change Graeme Gregory
2009-09-30 7:58 ` [PATCH] glibc_2.9.bb : add already existing OE patch arm-lowlevellock-include-tls.patch Graeme Gregory
2009-09-30 10:59 ` Philip Balister [this message]
2009-09-30 21:17 ` 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=4AC33A10.2040707@balister.org \
--to=philip@balister.org \
--cc=openembedded-devel@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.