From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev glibc: drop 2.4, since it is confirmed to be nonworking on arm
Date: Fri, 20 Oct 2006 07:39:32 +1000 [thread overview]
Message-ID: <20061019213932.GA30714@twibble.org> (raw)
In-Reply-To: <E1GadpR-0005SF-6I@linuxtogo.org>
On Thu, Oct 19, 2006 at 09:45:21PM +0200, "koen commit" wrote:
> glibc: drop 2.4, since it is confirmed to be nonworking on arm
Hmm, was this really necessary? Surely marking it broken for arm
would have been enough for now?
I'm sure I'm not the only one running glibc 2.4 on lots of non-arm
devices and now have to either add glibc 2.4 back in to OE locally
and/or get all my devices upgraded (which will happen, once I've
finished testing with glibc 2.5, no other glibc's build here except
2.4 and 2.5.)
And I'm sure there'll be a lot of people wondering why OE is suddenly
building an older version of glibc.
--
Jamie Lenehan <lenehan@twibble.org>
next parent reply other threads:[~2006-10-19 21:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1GadpR-0005SF-6I@linuxtogo.org>
2006-10-19 21:39 ` Jamie Lenehan [this message]
2006-10-20 7:04 ` [oe-commits] org.oe.dev glibc: drop 2.4, since it is confirmed to be nonworking on arm Marcin Juszkiewicz
2006-10-20 8:05 ` Koen Kooi
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=20061019213932.GA30714@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.