linux/poky.git/meta/conf/distro/include, branch sumo

yocto-uninative: Update to 2.4

2019-03-26T15:38:28+00:00

This supports glibc 2.29 which is appearing in distros like Ubuntu 19.04 (From OE-Core rev: 661ac7ed164965690a4334d372bf22f04c3bfd3a) Signed-off-by: Richard Purdie [Fixed up for Sumo context; no aarch64] Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

default-versions.inc: Make PREFERRED_VERSION_openssl* overwritable

2018-12-16T14:31:27+00:00

defaultsetup.conf and therefore default-versions.inc is sourced pretty late in bitbake.conf. default-versions.inc overwrites previous assignments of PREFERRED_VERSION_openssl. Assigning it with ?= allows other .conf files to assign correctly. in particular assignment in conf/local.conf and machine config is used instead of default. (From OE-Core rev: c9786adf81434e2d58247f55cf80fdd3131121e7) Signed-off-by: Richard Purdie

yocto-uninative: Upgrade to verson 2.3 which includes glibc 2.28

2018-11-16T16:33:08+00:00

This allows us to handle distros which contain glibc 2.28 such as Ubuntu 18.10. (From OE-Core rev: 5c7d9abcd611d23d4340f9a0aee2564f72158a0b) (From OE-Core rev: f01153e1782425756a40929ffb3fa72993b7a3b1) Signed-off-by: Richard Purdie [Fixed up for sumo context] Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

security_flags: disable static PIE in glibc

2018-10-10T12:26:25+00:00

Static PIE doesn't work entirely right in GCC 7, for example ldconfig on ARM with the flags enabled will something segfault during initialisation. To mitigate this until we have GCC 8 integrated, don't enable static PIE. (From OE-Core rev: 502de6f5db232a104eb269782a690f52fd665ef4) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Upgrade to version 2.2

2018-08-01T21:59:23+00:00

This version adds nativesdk-libnss-nis to resolve glibc symbol issues We need this to avoid symbol mismatch issues for binaries that use this on newer systems which then won't run on older ones where it isn't present. (From OE-Core rev: 98c7ab9cf32765d604c35dc69bc7bd90e94fc8f3) (From OE-Core rev: 026408c9d90e6241ce1b3d4cadefc48b7aba1734) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Update to version 2.1

2018-07-02T10:41:26+00:00

This fixes issues with fontforge-native. (From OE-Core rev: cec85a6fcadc24fd266fa34631cb095e0a773c1a) (From OE-Core rev: 57ecdffd14b671e09ec90a0d0ff4bba4efec43c0) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

yocto-uninative: Update to version 1.9 (fedora28 compatible)

2018-04-18T17:57:06+00:00

This includes the libxcrypt change which allows uninative to work on fedora28. (From OE-Core rev: 4b27ab6487a54b42a52aa16e98ea4d19fa62b5ae) (From OE-Core rev: 0685eb697f1dfa3b858b6e594cbd8e6070b4fbb8) Signed-off-by: Richard Purdie

distro: default: Change Go default version to 1.9

2018-04-13T15:58:07+00:00

For the time being, there is a serious bug[1] in Go 1.10 when it comes to use the shared runtime support which cases problems in multiple projects. 1. https://github.com/golang/go/issues/24640 It is still unclear if the problem arises from a bug inside the compiler itself or it makes a real problem more visible. Either way, using 1.10 as default seems to be a risk so we are changing back to 1.9 for now. Refs: [YOCTO: #12631] (From OE-Core rev: c5b5055d2dc04317a7a64c150046a6435a6805c2) Signed-off-by: Otavio Salvador Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

nativesdk-postinst-intercept: remove the recipe

2018-04-05T13:49:07+00:00

Its use required a script from an external repo which hasn't been updated in 4 years, the recipe itself is out of date (doesn't install all intercepts), and there is no oe-selftest or documentation for this. If anyone still wants this, please do it in a separate layer. (From OE-Core rev: 1fbae102fde54c9e7a0d74a4cda9900cd17640d6) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

default-distrovars: set default KERNEL_IMAGETYPE(S)

2018-03-31T08:48:42+00:00

With the change from assuming kernels will be named "vmlinuz" everywhere, to instead using KERNEL_IMAGETYPE, we require that KERNEL_IMAGETYPE is set to something. Instead of setting the default in multiple individual files, set it in default-distrovars.inc. x86(-64) arches get bzImage as the default. Others get zImage as per meta/conf/documentation.conf. Also set KERNEL_IMAGETYPES, as we will eventually be switching away from KERNEL_IMAGETYPE. Thanks to Andre McCurdy for the arch defaults part. (From OE-Core rev: a57d784211a39587538094425ee0246e9ddfbf9d) Signed-off-by: California Sullivan Signed-off-by: Richard Purdie