Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] uclibc-git: Fix build on x86 and move to latest master
Date: Tue, 26 Mar 2013 15:58:38 -0700	[thread overview]
Message-ID: <DDFE5CA4-5FBE-4338-928B-533D38D81DFD@gmail.com> (raw)
In-Reply-To: <1364338373.3097.117.camel@ted>


On Mar 26, 2013, at 3:52 PM, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:

> On Tue, 2013-03-26 at 14:48 -0700, Khem Raj wrote:
>> debugedit from rpm has unearthed a bug in uclibc
>> where it was mixing stabs with elf/dwarf
>> 
>> Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> ---
>> meta/recipes-core/uclibc/uclibc-git.inc            |    5 +-
>> .../0001-i386-sysdep.h-Remove-STABS_-macros.patch  |   71 ++++
>> ...-Move-aeabi_read_tp-to-uclibc_nonshared.a.patch |    8 +-
>> .../uclibc/uclibc-git/posix_fallocate.patch        |  408 --------------------
>> .../uclibc/uclibc-git/uclibc-execvpe.patch         |  163 --------
>> 5 files changed, 77 insertions(+), 578 deletions(-)
>> create mode 100644 meta/recipes-core/uclibc/uclibc-git/0001-i386-sysdep.h-Remove-STABS_-macros.patch
>> delete mode 100644 meta/recipes-core/uclibc/uclibc-git/posix_fallocate.patch
>> delete mode 100644 meta/recipes-core/uclibc/uclibc-git/uclibc-execvpe.patch
> 
> git am really doesn't like applying this, is there a tree I can pull it
> from somewhere?
> 

OK pushed to a branch

git://git.openembedded.org/openembedded-core-contrib kraj/uclibc-upgrade

> Cheers,
> 
> Richard
> 




      reply	other threads:[~2013-03-26 23:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 21:48 [PATCH] uclibc-git: Fix build on x86 and move to latest master Khem Raj
2013-03-26 22:52 ` Richard Purdie
2013-03-26 22:58   ` Khem Raj [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=DDFE5CA4-5FBE-4338-928B-533D38D81DFD@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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