Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: core glibc. Without this oabi compile of glibc doesnt work.
Date: Wed, 30 Sep 2009 11:34:08 +0200	[thread overview]
Message-ID: <h9v8mg$ivq$2@ger.gmane.org> (raw)
In-Reply-To: <1254297107-3475-1-git-send-email-dp@xora.org.uk>

Acked-by: Koen Kooi <koen@openembedded.org>


On 30-09-09 09:51, Graeme Gregory wrote:
> Graeme
>
>  From 74bad1b44410e3df4d13db286e008b5777146340 Mon Sep 17 00:00:00 2001
> From: Graeme Gregory<dp@xora.org.uk>
> Date: Wed, 30 Sep 2009 08:50:17 +0100
> Subject: [PATCH] glibc_2.9.bb : add already existing OE patch arm-lowlevellock-include-tls.patch
>
> 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





      reply	other threads:[~2009-09-30  9:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-30  7:51 core glibc. Without this oabi compile of glibc doesnt work Graeme Gregory
2009-09-30  9:34 ` Koen Kooi [this message]

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='h9v8mg$ivq$2@ger.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox