[oe] [RFC] Bring PREFERRED_LIBC to all distros
Tom Rini
trini at kernel.crashing.org
Tue Apr 28 20:55:20 UTC 2009
On Tue, Apr 28, 2009 at 01:30:09PM -0700, Khem Raj wrote:
> On (27/04/09 07:19), Tom Rini wrote:
> > Hey all. I've created a new branch, trini/add-libc-overrides which does
> > the following:
> > - Make every distro declare PREFERRED_LIBC, either outright or
> > overridable.
>
> may be you should call it something like SYSTEM_LIBC
OK, will rework and get a new branch up sometime soon.
> > - For Angstrom/foonas have DISTROVAR ?= ${PREFERRED_LIBC},
> > PREFERRED_LIBC ?= default
> > - Add conf/distro/include/{eglibc,glibc,uclibc}.inc that have:
> > - Add 'glibc' to OVERRIDES for eglibc/glibc and 'uclibc' for
> > uclibc.inc
>
> what about klibc so some distro's use klibc too ?
Not that I could see. At least not as the only libc.
> > That last change was required so that a number of distros would parse
> > without trying to build say both glibc_2.3.3 and glibc_2.9 (for
> > virtual-libc-dev) when I ran bitbake -g meta-toolchain minimal-image.
> >
> > The next step, once something like this goes in, would be to change all
> > of the overrides that test for uclibc (or glibc) from
> > linux/linux-gnueabi vs linux-uclibc/linux-uclibcgnueabi to just
> > linux_glibc vs linux_uclibc.
>
> only those two ? or one for each libc we have.
Until eglibc / glibc need different overrides, there's no need to have
them be different. uClibc isn't always done correctly however as you
have to catch both (ie the USE_NLS thing in the gcc recipes isn't right
for every version). And if we add another libc, we'll add another
override of course.
--
Tom Rini
More information about the Openembedded-devel
mailing list