All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev glibc 2.4: Apply recently added patches only fo x86.
Date: Thu, 28 Sep 2006 23:27:13 +1000	[thread overview]
Message-ID: <20060928132713.GA32288@twibble.org> (raw)
In-Reply-To: <E1GStq9-0003dN-FU@linuxtogo.org>

On Thu, Sep 28, 2006 at 01:14:05PM +0200, "pfalcon commit" wrote:
> glibc 2.4: Apply recently added patches only fo x86.
> * Fixes breakage on ARM.
> * Don't bump PR (previous commit neither did), to save long rebuilds.
> Few people affected should use "bitbake glibc -c rebuild".
> * Fixes #1443.
> * Approved by Michael 'Mickey' Lauer <mickey at tm.informatik.uni-frankfurt de>.

I've tested here and those two patches break glibc 2.4 for my main
targets which are sh4 (titan), i486 (wrap) and i586 (epia), building
on an x86_64 host. The breakage basically exactly the same as in
#1443.

I'm not sure what "x86" problem is that they are meant to fix (look
like they are just wiring up syscalls to use in place of glibc equivs
for the *at calls), but at least for me they actually break things on
i486 and i586.

Looks to me like the need more thinking/testing before being included
for anything.

-- 
 Jamie Lenehan <lenehan@twibble.org>



       reply	other threads:[~2006-09-28 13:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1GStq9-0003dN-FU@linuxtogo.org>
2006-09-28 13:27 ` Jamie Lenehan [this message]
2006-09-28 15:43   ` [oe-commits] org.oe.dev glibc 2.4: Apply recently added patches only fo x86 Michael 'Mickey' Lauer
2006-09-28 21:39     ` Jamie Lenehan
2006-09-28 22:06       ` Michael 'Mickey' Lauer
2006-09-28 23:30         ` Jamie Lenehan
2006-09-29  1:01           ` Jamie Lenehan
2006-09-29  8:59             ` Michael 'Mickey' Lauer

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=20060928132713.GA32288@twibble.org \
    --to=lenehan@twibble.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.