[oe] [PATCH] angstrom-2008.1: use linux-libc-headers 2.6.24 for hipox machine

[Koen Kooi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10-05-10 09:36, Steffen Sledz wrote:
>>>>>  #This is unrelated to the kernel version, but userspace apps (e.g. HAL) require a recent version to build against
>>>>> -PREFERRED_VERSION_linux-libc-headers 	= "2.6.31"
>>>>> +PREFERRED_VERSION_linux-libc-headers       ?= "2.6.31"
>>>>> +PREFERRED_VERSION_linux-libc-headers_hipox ?= "2.6.24"
>>>>
>>>> NACK, that creates undefined behaviour for multimachine builds.
>>
>>> -PREFERRED_VERSION_linux-libc-headers 	= "2.6.31"
>>> +PREFERRED_VERSION_linux-libc-headers       = "2.6.31"
>>> +PREFERRED_VERSION_linux-libc-headers_hipox = "2.6.24"
>>
>>> Is this better?
>>
>> No, it still changes the headers for one machine, which leads to
>> undefined behaviour for other machines using the same arch.
>> Any solution that doesn't mark *all* packages as machine specific for
>> hipox is going to cause that behaviour.
> 
> Would be a
> 
> -PREFERRED_VERSION_linux-libc-headers 	= "2.6.31"
> +PREFERRED_VERSION_linux-libc-headers  ?= "2.6.31"
> 
> acceptable to allow overwrites in local.conf?

This comes up about every month (search the archives) and the answer
remains the same: no
This will introduce the same undefined behaviour that was pointed out
earlier.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFL58T7MkyGM64RGpERApf+AJ9vJq9lk5TnCW6ykMU/QzFyTZvqtQCfY5SI
HV39oHD0RIw4Y4sCFY5QpqY=
=LzFt
-----END PGP SIGNATURE-----