>>>> #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? BTW: I did not found any fallback handling for inotify_init1 (added with 2.6.27) in the glibc. Regards, Steffen _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
