linux/poky.git/meta/conf, branch dizzy

layer.conf: Add missing dependency for allarch package initramfs-framework

2016-01-30T12:03:13+00:00

Similiarly to the other previous changes, add a missing allarch package dependency for initramfs-framework on udev. (From OE-Core rev: 685cc8a2922d51f7b1a255f11c72233ae572e2b2) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

layer.conf: Add several allarch dependency exclusions

2016-01-30T12:03:13+00:00

These are dependencies that our allarch packages have in OE-Core that cause those allarch packages to rebuild every time MACHINE changes. With these changes, OE-Core allarch packages all have a common sstate signatures and no longer rebuild. (From OE-Core rev: 63bff90fa4fb4a95e8c79f9f8e5dd90ae1dfc69d) (From OE-Core rev: 0d07fd7496c1f86538341eac43753f031583e2c4) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

security_flags: disable PIE on expect

2015-02-11T17:40:10+00:00

Disable PIE in expect as otherwise it tries to link the shared library as an executable. (From OE-Core rev: fe1f5c90eede593100fe57630d39cf329e59ef8f) (From OE-Core rev: fdf9e8e4679bb04e89222034ba999ae3bee63938) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

security_flags: disable pie support for libaio, blktrace and ltp

2015-02-11T17:40:05+00:00

libaio when built with pie and fpie does not link correctly with blktrace or ltp so we need to disable those flags until a better solution comes along. (From OE-Core rev: 4fbf13a6c28fc1170a4defbf50032546a14eaa59) (From OE-Core rev: b93c62e03724defa6a1465575c7db95485be37fb) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

bitbake.conf: add PKGDATA_DIR to BB_HASHBASE_WHITELIST

2015-02-11T17:40:05+00:00

In meta/conf/bitbake.conf, PKGDATA_DIR is default to: PKGDATA_DIR = "${STAGING_DIR_HOST}/pkgdata" But in meta/conf/multilib.conf, PKGDATA_DIR is set as: PKGDATA_DIR = "${STAGING_DIR}/${MACHINE}/pkgdata" When multilib enabled, linux-libc-headers cache will be machine specific: $ bitbake-diffsigs sstate-cache/1a/sstate:linux-libc-headers:ppce6500-poky-linux:3.17.7:r0:ppce6500:3:1a0c3934d91479fd7242a5b1d407d155_package.tgz.siginfo sstate-cache/28/sstate:linux-libc-headers:ppce6500-poky-linux:3.17.7:r0:ppce6500:3:28c918e8f9f4a4cfceb3a38b258f7501_package.tgz.siginfo basehash changed from 8d3158bbddcee612fa30badd05f47b8e to 68ac258fc6c8e489f360fde3123a5894 Variable MACHINE value changed from 'b4420qds' to 'b4860qds' (From OE-Core rev: 02af85cbaac660e92c760db41a1efce9e359248f) Signed-off-by: Ting Liu Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

tcmode-default.inc: use GCCVERSION for gcc-source

2015-01-06T14:13:44+00:00

This was missing leading to gcc-source- being built when using gcc-cross- with GCCVERSION=bar. (From OE-Core rev: fa249f347b3453537ee6aaea0d3bb75cfe7a75d1) (From OE-Core rev: e7f94f589b17c64ae2fd72c8dda41c113ff399c9) Signed-off-by: Koen Kooi Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

default-distrovars: add gcc-source recipe to the GPLv3 whitelist

2015-01-06T14:13:43+00:00

gcc-source is a convenience recipe to save duplicate copies of the GCC source tree and should be whitelisted for GPLv3 avoidance along with the rest of GCC. (From OE-Core rev: fd58d0e920707198caf62ffef50b67c7c7882c69) (From OE-Core rev: 6ec22ea1d40256c0b780c6ba533413684fa02c8e) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

security_flags: Fix typo for cups

2014-12-31T10:19:08+00:00

(From OE-Core rev: 146b1ea632294b2830e2cfe2d1258d48cd0c0e85) (From OE-Core rev: 7ea83ed3c662312fa17718bb4358063f1e248021) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

bluez-hcidump: select provider as bluez4 or bluez5

2014-12-31T10:19:01+00:00

bluez-hcidump was a separate package in bluez4, but was integrated into bluez5. (From OE-Core rev: 0dcaea0fcf38f0e382eda11e74ded1daeb98a8ac) (From OE-Core rev: 0c18fdd44accbcc04731e1e3f1ce1faa5e350db9) Signed-off-by: Peter A. Bigot Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

bitbake.conf: pseudo fall back to last-resort passwd files

2014-12-31T10:18:50+00:00

Recipe packaging for the target requires permissions that are consistent with meta/files/fs-perms.txt which specifies certain user and group names. In the early parts of a target build base-passwd is not yet available to provide the target /etc files used for user/group lookup. Allow pseudo to fall-back to the last-resort files it installs if the target ones aren't there yet. (From OE-Core rev: 071d364b7a758ba5e546bb18c5816ac4c2e6747c) (From OE-Core rev: fdf7e1829810df75d180c06db615f9771f46d592) Signed-off-by: Peter A. Bigot Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie