Re: problems compiling glibc_2.9-r37.4 under Angstrom

[Koen Kooi <k.kooi@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@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
and not setting PREFERRED_VERSION for recipes, using source mirrors or
using things like insane.bbclass. As expected, you had to use pretty
much all those to get minimal to build something remotely usefull.

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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFNOrsQMkyGM64RGpERAm+UAJ9YGoCY6P8irFVlcWPF3N5TinD93gCfXU2V
2BBSC/hC7I7ynDgUAps4VuQ=
=RB3v
-----END PGP SIGNATURE-----