linux/poky.git/meta/recipes-kernel/linux-libc-headers/linux-libc-headers.inc, branch yocto-3.0.3

linux-libc-headers: update to 5.x headers

2019-03-06T16:44:37+00:00

Updating the linux-libc-headers to the 5.x kernel variant to match the latest reference kernel in the 2.7 release. We have two patches refreshed for context changes, and three patches dropped since they have been merged to the mainline kernel and are no longer necessary. (From OE-Core rev: f6c825c41e3d4c14ae4ba0b2a07cc41d538e0d61) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

linux-libc-headers: Don't do useless configuration

2018-09-13T16:38:07+00:00

There's no point in configuring Linux kernel before headers installation. Moreover in come cases it might lead to problems on kernels starting from 4.17 with architecture or platfrom sets CROSS_COMPILE variable automatically, see [1]. Also note Buildroot doesn't do that kind of configuration as well, see [2]. And while at it convert empty do_compile to noexec as well. [1] https://lkml.org/lkml/2018/9/12/486 [2] https://git.buildroot.org/buildroot/tree/package/linux-headers/linux-headers.mk#n106 (From OE-Core rev: 681ea847d760e69623b4ed110a6078f37ac3ec63) Signed-off-by: Alexey Brodkin Signed-off-by: Richard Purdie

libc-headers: update to 4.18

2018-08-28T09:30:28+00:00

Updating to the 4.18 headers to match the newest kernel that will be part of the release. 4.18 brings a requirement on bison-native to the libc-headers, since it is required as part of the configuration steps. We also tweak the license md5sum, since the kernel now includes SPDX headers in the license file and that changes our sum. (From OE-Core rev: c36a5e21b711cd577a2186a5267d46bb4323acc1) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

linux-libc-headers: To fix build error when enable mutilib on aarch64 Big endian.

2018-07-10T16:32:59+00:00

(From OE-Core rev: 1c31fa6929fc97e2fb0c4fbfcc66c789c39c1117) Signed-off-by: Lei Maohui Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

linux-libc-headers: multilib_header asm/kvm_para.h and asm/bpf_perf_event.h

2018-05-04T12:28:05+00:00

When building SDK via populate_sdk for qemuarm64 with multilib enabled, we would have conflict about bits/floatn.h at populate_sdk time. file /usr/include/asm/bpf_perf_event.h conflicts between attempted installs of lib32-linux-libc-headers-dev-4.15.7-r0.armv7vehf_vfp and linux-libc-headers-dev-4.15.7-r0.aarch64 file /usr/include/asm/kvm_para.h conflicts between attempted installs of lib32-linux-libc-headers-dev-4.15.7-r0.armv7vehf_vfp and linux-libc-headers-dev-4.15.7-r0.aarch64 Apply oe_multilib_header on these header files to fix the problem. (From OE-Core rev: 89b4e77129990b842e2ca917b98473ec58205e88) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

linux-libc-headers: fix upstream version check

2017-04-29T10:17:23+00:00

(From OE-Core rev: 83d55bcc63510d3704078f19c255c524d8fffc39) Signed-off-by: Alexander Kanavin Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

linux-libc-headers: Remove reference to cross-linkage

2017-03-31T09:10:29+00:00

This is long dead (thankfully), remove stale reference/comment. (From OE-Core rev: 2340fcb1af3c9ca350dba89d48a44f414277d1a8) Signed-off-by: Richard Purdie

linux-libc-headers: Allow arm kernel headers to coexist on 32/64 bit

2017-03-31T09:10:29+00:00

Its rather sad we need to do this but in order to make combined 32 and 64 bit SDKs work, we need a common set of headers and this is the delta that allows things to work. It only applies on arm. (From OE-Core rev: 592ae8e521a3926e8e5f87e2364e1ba8d92b8c2d) Signed-off-by: Richard Purdie

linux-libc-headers: Add inherit of pkgconfig

2017-03-04T23:18:20+00:00

pkg-config is used by the kernel build system when creating the configuration tools. (From OE-Core rev: 8e756a808267da26c5c93729438e5757146be534) Signed-off-by: Peter Kjellerstedt Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta/scripts: Various getVar/getVarFlag expansion parameter fixes

2017-01-09T13:39:11+00:00

There were a few straggling expansion parameter removals left for getVar/getVarFlag where the odd whitespace meant they were missed on previous passes. There were also some plain broken ussages such as: d.getVar('ALTERNATIVE_TARGET', old_name, True) path = d.getVar('PATH', d, True) d.getVar('IMAGE_ROOTFS', 'True') which I've corrected (they happend to work by luck). (From OE-Core rev: 688f7a64917a5ce5cbe12f8e5da4d47e265d240f) Signed-off-by: Richard Purdie