libc-common.bbclass and uclibc

libc-common.bbclass and uclibc

[Manuel Bessler]

I'm one of the (seemingly few) people using OE/Yocto on a uclibc platform.

Since I'm using a vendor-supplied toolchain, I had to make a few changes to
keep the build from trying to build uclibc despite it was being supplied via
the toolchain.

Comparing with the external-csl-toolchain recipe I found that it
"require"s eglibc-package.inc,
so I created a uclibc-package.inc. This fixed the above issue of
trying to build uclibc despite
it was already provided by the external toolchain.

In creating uclibc-package.inc I tried to follow closely how
eglibc-package.inc was implemented.

This has worked for me well until I started on the nativesdk with
external toolchain.
I noticed that my external-toolchain-xxx-cross-canadian_xxx.bb recipe
(which provides
uclibc*, binutils-cross-canadian, and gcc-cross-canadian) created
libc6, libc6-dev, and libc6-dbg
packages.

A quick search revealed meta/classes/libc-common.bbclass referencing libc6.
Function populate_packages_prepend() seems to just overwrite
PKG_${BPN} with libc6.

=========================================
python populate_packages_prepend () {
        if d.getVar('DEBIAN_NAMES', True):
                bpn = d.getVar('BPN', True)
                d.setVar('PKG_'+bpn, 'libc6')
...
=========================================

It does not seem to care about uclibc.
Maybe libc-common.bbclass is only for eglibc and might need a better name?
Since this is checking for "DEBIAN_NAMES" and I guess debian is not
uclibc based,
maybe this code is not really the issue...

Do I just need to create a uclibc-common.bbclass ?

Thanks,
Manuel

Re: libc-common.bbclass and uclibc

[Chris Larson]

On Thu, Jul 26, 2012 at 2:51 PM, Manuel Bessler
<manuel.bessler@gmail.com> wrote:
> It does not seem to care about uclibc.
> Maybe libc-common.bbclass is only for eglibc and might need a better name?
> Since this is checking for "DEBIAN_NAMES" and I guess debian is not
> uclibc based,
> maybe this code is not really the issue...
>
> Do I just need to create a uclibc-common.bbclass ?

Debian-originated shared library-based package renaming occurs
regardless of what C library you use, and isn't relevant.
-- 
Christopher Larson

Re: libc-common.bbclass and uclibc

[Phil Blundell]

On Thu, 2012-07-26 at 17:51 -0400, Manuel Bessler wrote:
> =========================================
> python populate_packages_prepend () {
>         if d.getVar('DEBIAN_NAMES', True):
>                 bpn = d.getVar('BPN', True)
>                 d.setVar('PKG_'+bpn, 'libc6')
> ...
> =========================================

That particular piece of code does seem bogus for many reasons and
should probably go away.  I think it is a historical relic.

But, that said, libc-common.bbclass is poorly named and is really
specific to (e)glibc.  You don't want to use that for uclibc.

p.

Re: libc-common.bbclass and uclibc

[Manuel Bessler]

On Thu, Jul 26, 2012 at 6:17 PM, Phil Blundell <philb@gnu.org> wrote:
> On Thu, 2012-07-26 at 17:51 -0400, Manuel Bessler wrote:
>> =========================================
>> python populate_packages_prepend () {
>>         if d.getVar('DEBIAN_NAMES', True):
>>                 bpn = d.getVar('BPN', True)
>>                 d.setVar('PKG_'+bpn, 'libc6')
>> ...
>> =========================================
>
> That particular piece of code does seem bogus for many reasons and
> should probably go away.  I think it is a historical relic.
>
> But, that said, libc-common.bbclass is poorly named and is really
> specific to (e)glibc.  You don't want to use that for uclibc.

Ok, thanks, good to know. I just confirmed that my build indeed
succeeds without it.

Thanks,
Manuel