On Wed, May 27, 2020 at 2:52 PM Phil Blundell via lists.openembedded.org <pb=pbcl....@lists.openembedded.org> wrote: > > On Wed, May 27, 2020 at 02:46:24PM -0700, Khem Raj wrote: > > and building userspace against way newer kernel-headers with older > > kernel underneath has unintended > > consequences. > > Can you be more specific? If this doesn't work, it's just a bug and > should be fixed. What problems are you having?
I don't have an up to date example, but I've been using kernel version specific libc headers for all my projects for many years. The issue which prompted me to do that was run time crashes from libcap-ng and the historical commit message was: ---- linux-libc-headers: use 3.3.8 kernel header files for mips platforms If libcap-ng is unable to probe kernel capabilities at runtime then it will assume the kernel supports all features defined by the libc kernel headers. Since our default libc kernel headers (linux 3.14) define capabilities which are not available in linux 3.3 based stblinux kernel used for our MIPS platforms, that causes runtime crashes. As a workaround, force an older version of linux-libc-headers for all MIPS platforms to try to remove that discrepancy between the kernel's capabilities and those defined in the libc kernel headers. ---- The risk of using bleeding edge linux-libc-headers with an older kernel may be low, it's not zero. Since OE testing doesn't appear to include any coverage of older kernels, I'm not sure why I should be the guinea pig and take the risk!
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138825): https://lists.openembedded.org/g/openembedded-core/message/138825 Mute This Topic: https://lists.openembedded.org/mt/74502640/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
