On Mon, 2010-05-10 at 10:34 +0200, Koen Kooi wrote: > -----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.
Perhaps the fact that this comes up once a month means the Angstrom folks may want to think about how to have a very clear to the user not compatible with the main feeds and so on custom distribution, but that doesn't start out with cp conf/distro/angstrom-2008.1.conf conf/distro/mystrom.conf ? -- Tom Rini <tom_r...@mentor.com> Mentor Graphics Corporation _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel