From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Building older glibc
Date: Wed, 13 May 2009 16:12:37 +0200 [thread overview]
Message-ID: <1242223957.9015.6.camel@port4> (raw)
In-Reply-To: <87bppxe07v.wl%peter@chubb.wattle.id.au>
On Wed, 2009-05-13 at 21:00 +1000, Peter Chubb wrote:
> Is there a trick to building an older glibc than the head? I'm
> building for x86, and I need a libc.a that'll run against a 2.6.10
> kernel --- so I've tried
> bitbake glibc-2.3.2
> (and 2.3.5)
> And I see :
> ...
> | configure: loading site script /usr/src/oe-sel4/openembedded/site/common
> | configure: loading site script /usr/src/oe-sel4/openembedded/site/common
> | configure: error: add-on directory "nptl" does not exist
> | FATAL: oe_runconf failed
> NOTE: Task failed: /usr/src/oe-sel4/tmp/work/i686-oe-linux/glibc-2.3.2-r20/temp/log.do_configure.17493
> NOTE: package glibc-2.3.2-r20: task do_configure: failed
> ERROR: TaskFailed event exception, aborting
>
> --
> Dr Peter Chubb http://www.gelato.unsw.edu.au peterc AT gelato.unsw.edu.au
> http://www.ertos.nicta.com.au ERTOS within National ICT Australia
I had the same requirements:
I have a 2.4 kernel that doesn't have:
*nptl
*eabi
so I tried to patch a recent glibc and at the end I end up choosing
uclibc...
The drawback is that it seriously affect my binary compatibility with
glibc(that is to say I can't run the proprietary software that came with
the device...but I want to get rid of that software anyway...so...)
I didn't try or look into eglibc and I'm interested in knowing if it
require nptl
Denis.
next prev parent reply other threads:[~2009-05-13 14:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 11:00 Building older glibc Peter Chubb
2009-05-13 14:12 ` GNUtoo [this message]
2009-05-13 14:57 ` Tom Rini
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=1242223957.9015.6.camel@port4 \
--to=gnutoo@no-log.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.