[OE-core] [PATCH 04/10] glibc: bring back the needed support for glibc recipes

[Richard Purdie]

On Thu, 2011-08-04 at 16:18 -0700, Khem Raj wrote:
> On 08/04/2011 08:01 AM, nitin.a.kamble at intel.com wrote:
> > From: Nitin A Kamble<nitin.a.kamble at intel.com>
> >
> > Signed-off-by: Nitin A Kamble<nitin.a.kamble at intel.com>
> > ---
> >   meta/conf/distro/include/tclibc-glibc.inc   |   32 +++++++++++++++++++++++++++
> >   meta/conf/distro/include/tcmode-default.inc |    5 ++++
> >   2 files changed, 37 insertions(+), 0 deletions(-)
> >   create mode 100644 meta/conf/distro/include/tclibc-glibc.inc
> >
> > diff --git a/meta/conf/distro/include/tclibc-glibc.inc b/meta/conf/distro/include/tclibc-glibc.inc
> > new file mode 100644
> > index 0000000..823195c
> > --- /dev/null
> > +++ b/meta/conf/distro/include/tclibc-glibc.inc
> > @@ -0,0 +1,32 @@
> > +#
> > +# glibc specific configuration
> > +#
> > +
> > +LIBCEXTENSION = "${@['', '-gnu'][(d.getVar('ABIEXTENSION', True) or '') != '']}"
> 
> why is this specific to glibc and not eglibc ?

eglibc has the same code.

> since glibc is deleted from metadata this file should go away too
> if its for external toolchains then they could use tclibc-eglibc.inc
> or tclibc-uclibc.inc as needed.
> 
> I am in favour of generally using linux-gnu extention for eglibc/glibc
> based systems.

I think it should be up to the user. We've ensured the recent changes
don't change the defaults, you can certainly use linux-gnu if you want
(but it will cause issues as not everything accepts that format as
things stand iirc).

Cheers,

Richard