linux/poky.git/meta/conf, branch 2.6_M3

layer.conf: Add thud to LAYERSERIES_CORENAMES

2018-09-24T11:30:16+00:00

With the release approaching, add thud to LAYERSERIES_CORENAMES and update oe-core to use this release series. "sumo" will be removed during M4 in the next couple of weeks so people need to start updating their master layers in preperation for release. (From OE-Core rev: 986792481fa005fe136fd4b4e388042492b1ad8a) Signed-off-by: Richard Purdie

yocto-uninative: Add aarch64 uninative tarball checksum

2018-09-20T16:06:00+00:00

(From OE-Core rev: 957a2f95b839f2d871c658d6e8ea8c0f4d6c41e5) Signed-off-by: Richard Purdie

maintainers.inc: Update package owners

2018-09-20T12:41:32+00:00

update Intel owners (From OE-Core rev: a6de4b1809e90d02a865c56ec8269bdfa3ceec0a) Signed-off-by: Maxin B. John Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

libressl: remove recipe

2018-09-20T12:41:31+00:00

Since openssh support oepnssl 1.1.x, there is no reason to keep libressl. (From OE-Core rev: 30121a78555574f49b321566fcab172417bdf3e3) Signed-off-by: Hongxu Jia Signed-off-by: Richard Purdie

tune-core2: use n270 instead of core2duo

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

Fixes warnings in builds using core2-32 tune: warning: TCG doesn't support requested feature: CPUID.80000001H:EDX.syscall [bit 11] warning: TCG doesn't support requested feature: CPUID.80000001H:EDX.lm [bit 29] when executing postinsts using qemu-i386. i386 target doesn't enable CPUID_EXT2_SYSCALL and CPUID_EXT2_LM [1] while cpu choice of core2duo that we use for core2-32 TUNE does [2]. Use n270 cpu instead to use with qemu which supports SSSE3 and doesn't have these bits enabled [3]. [1] https://github.com/qemu/qemu/blob/master/target/i386/cpu.c#L739 [2] https://github.com/qemu/qemu/blob/master/target/i386/cpu.c#L1439 [3] https://github.com/qemu/qemu/blob/master/target/i386/cpu.c#L1603 Fixes [YOCTO #12916] (From OE-Core rev: 3db567d7835c6bb158d0f6c5b5533835a0181c45) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

bitbake.conf: Make BUILD_OPTIMIZATION respect to DEBUG_BUILD

2018-09-13T06:42:28+00:00

We may also need debug native tools, so make BUILD_OPTIMIZATION respect to DEBUG_BUILD, otherwise, we need set CFLAGS in the recipe which isn't convenient. (From OE-Core rev: 5db09f7ad007d1def009a60d7d9bf9c13c0faa4e) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

oe/utils.py: Add vartrue()

2018-09-13T06:42:28+00:00

It can be used to simplify code like: "${@['iffalse', 'iftrue'][var]}" (From OE-Core rev: fc5a5af7bc3619f575988a75efc0c4fe15478b2d) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

yasm: remove

2018-09-11T11:09:10+00:00

Nothing in oe-core is using yasm now that gstreamer-libav and ffmpeg are using nasm, so remove it from oe-core. (From OE-Core rev: b7f3f7ecfdf26129c5df2d3ee14e73c4633ea5a3) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

tclibc-baremetal.inc: Remove BASEDEPENDS on compilerlibs

2018-09-11T08:05:35+00:00

Without a libc the gcc-runtime provider of compilerlibs does not compile. As such avoid the default dependence on the virtual/${TARGET_PREFIX}compilerlibs provider. (From OE-Core rev: 61eead0cdd1f44d8c850f8e4c7389ef444bcd591) Signed-off-by: Nathan Rossi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

tclibc: For newlib and baremetal disable some security features

2018-09-11T08:05:35+00:00

With GCCPIE being enabled by default with security_flags.inc the compiler will by default attempt to compile and link programs as PIE. The targets that use newlib and baremetal in general do not support PIE or are otherwise unable to use it due to how embedded targets are compiled and executed. As such it makes sense to disable PIE by default for these libc's in order to prevent build failures. For baremetal tclibc there are no libc features or implementation as such there is no implementation for the strong stack protector by default. (From OE-Core rev: dfe434b793c156a87b5ead5cb85fe60d920d69d3) Signed-off-by: Nathan Rossi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie