linux/poky.git/meta/conf, branch yocto-2.4

bitbake.conf: Adds ipv6 to DISTRO_FEATURES_NATIVE

2017-10-16T22:53:45+00:00

Before we introduced DISTRO_FEATURES_NATIVE on commit: db1f1adace58763c35774e3fdfeaac5c3ca646fd ipv6 was enabled by default on DISTRO_FEATURES via DISTRO_FEATURES_LIBC hence for example python-native was built with ipv6 support. After this, ipv6 was automatically disabled on DISTRO_FEATURES. On some packages (python) this may cause errors when they try to download something on their do_compile stage. This patch adds ipv6 to DISTRO_FEATURES_NATIVE leaving it as it was before, to avoid errors like the one mentioned above [YOCTO #11978] (From OE-Core rev: a09184bf47323b63d9548d17cc1e4e694cb605a9) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie

bitbake.conf: add ssh to HOSTTOOLS_NONFATAL

2017-10-16T22:52:44+00:00

We changed to make tools required by testimage to be included conditionally. This resulted in users who use ssh for git fetching having failures. Add ssh to HOSTTOOLS_NONFATAL to make things work for the above situation. [YOCTO #12227] (From OE-Core rev: 50e7619aebae5351e9a41fe1b909a31b9e383f0a) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: add tools required by testimage to HOSTTOOLS conditionally

2017-10-09T09:09:09+00:00

Add tools required by testimage to HOSTTOOLS only when testimage is inherited. These tools, as described in the comment, are only required by the testimage task. So this change should not have negtive effect. This would also solve build error on hosts which miss some tool such as scp. (From OE-Core rev: 8ca61a5464743ff85b6d26886112750d6ddd13e0) Signed-off-by: Chen Qi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: Add 'id' to HOSTTOOLS

2017-10-07T22:20:40+00:00

The 'id' utility is used in 'rootfs_check_host_user_contaminated' rootfs-postcommand so it must be available. (From OE-Core rev: 6c054925d5f80790aea4cce6f8f83edc7da623b9) Signed-off-by: Otavio Salvador Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

arch-x86: Add x86-x32 to MACHINEOVERRIDES

2017-09-26T10:05:01+00:00

This is needed as an x32 more generic x32 override later in the OVERRIDES, currently linux-gnux32 is the first override, but we need a stronger (later in the list) x32 override to deal with some needed x32 dependency overrides. (From OE-Core rev: 364b3698b78e9fea59d24e3a3a5f4476be95f6d1) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

meta: drop True option to getVar calls

2017-09-26T10:05:01+00:00

Search made with the following regex: getVar ?\((.*), True\). (From OE-Core rev: dbc0eaf478feb3f752ae22fd184984494fc85d0a) Signed-off-by: Ming Liu Signed-off-by: Richard Purdie

conf: add maintainers.inc from meta-poky

2017-09-21T08:05:49+00:00

Signed-off-by: Richard Purdie

gawk: Enable native building

2017-09-18T10:07:31+00:00

Also update the ASSUME_PROVIDED in bitbake.conf to contain gawk-native as the dependency is passed in via HOSTTOOLS for native builds. This allows for recipes to depend on gawk-native, and have the dependency met if not already provided by the host tools. (From OE-Core rev: cbc396dd10488990c98bb6fd94c7d10a736d57c1) Signed-off-by: Nathan Rossi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

bitbake.conf: Add default FILESYSTEM_PERMS_TABLES

2017-09-18T10:07:29+00:00

If FILESYSTEM_PERMS_TABLES was not defined, the default was selected by the packages.bbclass. This made it difficult for a recipe or layer to 'append' to the default. Copy the default into the bitbake.conf, allowing future _append and += style actions. Default was remove from package.bbclass. If a value is not set, only the built-in perms fixes will be used. (From OE-Core rev: b65736e1b7161619a0c5972376d3e713ccf53850) Signed-off-by: Mark Hatle Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

meta/conf/layers.conf: Add ca-certificates as ABISAFE

2017-09-13T21:10:36+00:00

meta-oe was doing this before, but it was triggering a yocto-compat-script failure during the signature checking. The ca-certificates changing is ABISAFE, as the certificates themselves do not modify the compiles behavior of the applications. This should permit easier upgrades without as much rebuilding. The original value was set in meta-oe by commit ff7a4b13c4efeffc5853a93c6ff7265fa3d6c143. (From OE-Core rev: 583dca290c230fbc981c41fe91e8abeff616e633) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie