[oe] problems compiling glibc_2.9-r37.4 under Angstrom

[Frans Meulenbroeks]

2011/1/22 Koen Kooi <k.kooi at student.utwente.nl>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 22-01-11 01:21, Khem Raj wrote:
>> On Fri, Jan 21, 2011 at 3:03 AM, Koen Kooi <k.kooi at student.utwente.nl> wrote:
>> On 20-01-11 19:12, Víctor M. Jáquez L. wrote:
>>>>>
>>>>> In order to build native-sdk-image recipe, I found my self compiling
>>>>> glibc_2.9-r37.4, because it is the real provider of virtual-libc-dev (the
>>>>> toolchain does not truly provide it -but that is another bug [1]-).
>>>>>
>>>>> But the glibc_2.9-r37.4 configuration fails using the canonical
>>>>> arm-angstrom-linux-gnueabi- toolchain
>>
>> If you're using angstrom 2008, glibc 2.9 is built by default. Trying to
>> rebuild it won't work because it will be missing headers due to all the
>> -initial and -intermedia shuffle.
>> If you're using angstrom 2010, eglibc is built by default and should
>> providing virtual-libc-dev
>>
>>> yes angstrom-2010.x is a better option keep in mind its new so expect
>>> some churn every now and then.
>>
>>
>> Switching to minimal will only get you anguish, since it's broken by design.
>>
>>> Heh interesting :) It would help if you elaborate on the flaws so we
>>> can improve it and in turn improve OE in general
>
> The design involves not using PREFERRED_PROVIDER for things like bluez

Do you mean this?
minimal.conf:PREFERRED_PROVIDER_bluez-utils-dbus = "bluez4"
minimal.conf:PREFERRED_PROVIDER_bluez-libs       = "bluez-libs"
minimal.conf:PREFERRED_PROVIDER_bluez-utils      = "bluez4"

> and not setting PREFERRED_VERSION for recipes, using source mirrors or

You mean like this:
minimal.conf:PREFERRED_QT_VERSION ?= "4.7.1"
minimal.conf:PREFERRED_VERSION_qt4-tools-native = "${PREFERRED_QT_VERSION}"
minimal.conf:PREFERRED_VERSION_qt4-tools-sdk = "${PREFERRED_QT_VERSION}"
minimal.conf:PREFERRED_VERSION_qt4-embedded = "${PREFERRED_QT_VERSION}"
minimal.conf:PREFERRED_VERSION_qt4-embedded-gles = "${PREFERRED_QT_VERSION}"
minimal.conf:PREFERRED_VERSION_qt4-x11-free = "${PREFERRED_QT_VERSION}"
minimal.conf:PREFERRED_VERSION_qt4-x11-free-gles = "${PREFERRED_QT_VERSION}"

minimal also includes sane-toolchain.inc which contains the preferred
versions of the toolchain.
(together with some other distros)

Yes there are less pinnings in minimal than in angstrom. Fortunately
not, I'd say. I assume this is because the minimal maintainers have
more confidence and trust in the package maintainers.

wrt the source mirrors.
I feel recipes should build without source mirror. However in some
cases (e.g. handhelds.org) a source mirror is useful. In my previous
reply I suggested to populate sources.openembedded.org. Those who need
it can use it.
If the sources for a recipe reside on a mirror only, the recipe
SRC_URI should be changed to reflect that. Whether a recipe fetches or
not should not depend on the distro.

> using things like insane.bbclass. As expected, you had to use pretty

get your facts straight. minimal uses insane.bbclass:
minimal.conf:INHERIT += "insane"
No idea when exactly it was added. I'm not the minimal maintainer),
but it is used now.

> much all those to get minimal to build something remotely usefull.

In my opinion it is more useful than a binary generator generating
untested (and probably unreproducible) images, but that is just my
opinion. If someone wants to play the digital equivalent of russian
roulette, who am I to deny it to them.
>
> As Philip points out, people are free to deliberately not use those
> advanced features, but they should also realize that any breakage due to
> that is entirely their own fault.

Have a nice weekend! Frans.