linux/poky.git/meta/classes, branch daisy

kernel: Added bc-native as DEPENDS

2017-09-11T09:48:04+00:00

The makefile checks for bc during for compilation [YOCTO #6781] (From OE-Core rev: a3778df1699ac8a1e80cae6886b41bfcbbebc016) Signed-off-by: Alejandro Hernandez Signed-off-by: Richard Purdie (cherry picked from commit c067e52cffe002de3b39aa1bced308dd532859c1) Signed-off-by: Andre McCurdy Signed-off-by: Richard Purdie

utils.bbclass: fix create_cmdline_wrapper

2015-03-11T14:41:38+00:00

Similar to commit 4569d74 for create_wrapper function, this commit fixes hardcoded absolute build paths in create_cmdline_wrapper. Otherwise we end up with incorrect paths in users of this function. For example the 'file' wrapper in current released toolchain: exec -a /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-fsl-arm/build/build/tmp/work/x86_64-nativesdk-pokysdk-linux/nativesdk-file/5.18-r0/image//opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/bin/file `dirname $realpath`/file.real --magic-file /opt/poky/1.7.1/sysroots/x86_64-pokysdk-linux/usr/share/misc/magic.mgc "$@" (From OE-Core rev: 49ab89eb9f83388e99069a4b53bdc4cba22bb6f3) (From OE-Core rev: 8503dee5a42fc0dc6dc6c79ce316aba1c91da6d1) Signed-off-by: Javier Viguera Signed-off-by: Richard Purdie

btrfs: create an empty file to build the fs in

2015-02-06T14:56:08+00:00

The newer btrfs-utils needs an empty file to build the filesystem in, so create an empty file and use it for the mkfs to build the fs in. [YOCTO #6804] (From OE-Core rev: afc44fad44261677c799558ffd35f4908556bce0) Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

update-rc.d: Allow to use different initscripts provider

2015-02-06T14:56:07+00:00

* until now all recipes were respecting VIRTUAL-RUNTIME_initscripts variable but commit bba835fed88c3bd5bb5bd58962034aef57c408d8 hardcoded "initscripts" runtime dependency (From OE-Core rev: 1cda75706d63c988a0fa9945bd320b71c8e8488a) Signed-off-by: Martin Jansa Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

update-rc.d/systemd: Remove OVERRIDES dependency

2014-09-29T16:58:35+00:00

Taking run-postinsts and building for two machines which have different OVERRIDES leads to two different sets of stamps for an allarch package. We don't need to depend on OVERRIDES in these classes, the end resulting variables are good enough. We can therefore exclude the dependency and allow a single package to be generated for run-postinsts. (From OE-Core rev: 6e875148f79a6877653a5bf95879b8cda1cacbc6) Signed-off-by: Richard Purdie Signed-off-by: Steffen Sledz Signed-off-by: Richard Purdie

useradd-staticids.bbclass: Fix for Bug 6633

2014-09-23T12:02:57+00:00

When using the useradd-staticids.bbclass under meta/classes, this error occurs: " - : Username does not have a static uid defined." There was a problem with the regular expression for parsing parameters, it was sometimes returning an empty string. I have fixed this by skipping empty strings. (From OE-Core rev: f249ef32709069a2680b92dc5a5b4f6545d014b7) (From OE-Core rev: 592f0dccaf1985194f40fc019a9d33b9623df37f) Signed-off-by: Fabrice Coulon Signed-off-by: Richard Purdie

crosssdk: Clear MACHINEOVERRIDES

2014-09-20T09:41:29+00:00

Without this, things like arm* can make it into OVERRIDES when we're building a compiler to build binaries for another architecture like x86. This can can lead to build failures dependning on the exact configuration and overrides. For example: MACHINE=imx53qsb bitbake gcc-crosssdk-initial-x86_64 -e | grep EXTRA_OECONF was showing an armv7 configuration option to gcc. (From OE-Core rev: d02cdf3ee88c7bbb93cecf094008858782deec3f) Signed-off-by: Richard Purdie

native/nativesdk: Clear MACHINEOVERRIDES

2014-09-20T09:41:29+00:00

In cases where we override variables e.g PACKAGE_ARCH conditionally and use a MACHINEOVERRIDE to qualify the override like PACKAGE_ARCH_ = "some target PACKAGE_ARCH" This would also be effective if this recipe is BBEXTENDED to native or nativesdk which is undesired This particular issue will cause wrong sysroot to be used for nativesdk case since PACKAGE_ARCH would have been modified and eventually changing value of STAGING_DIR_TARGET which we use as --sysroot option to cross and cross-canadian built SDK gcc (From OE-Core rev: 474234a362b4cda5f2f1afab369c98d4e0ca1b11) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

populate_sdk_base: Fix grep command usage on old hosts

2014-08-15T08:55:31+00:00

"man grep" on centos: -R, -r, --recursive Read all files under each directory, recursively; this is equivalent to the -d recurse option. "man grep" on a more recent ubuntu system: -r, --recursive Read all files under each directory, recursively, following symbolic links only if they are on the command line. This is equivalent to the -d recurse option. So we have an issue when the SDK installer (even with buildtools-tarball) is used on old hosts since it may try and dereference paths which it should not. This is caused by differences in the behaviour of grep -r on older systems. The fix is to wrap this in find so that only real files are found (as elsewhere in the script. [YOCTO #6577] (From OE-Core rev: 7986adeac16550b33f65fded39a55f668e0e543f) (From OE-Core rev: 11e83000b164340b7e261a62f074a0e0cb6d6282) Signed-off-by: Richard Purdie Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

kernel: don't copy .so.dbg files into kernel source install

2014-08-11T11:06:54+00:00

In 3.16+ x86-64 kernel builds produce a vdso64.so.dbg file. If this file is copied into the kernel source install multiple QA failures are triggered. Specifically, this file triggers a debug package split that results in files installed but not shipped, and invalid .debug file errors. By ensuring that .so files are not copied, we avoid this incorrect split with no impact on future build phases. (From OE-Core rev: 649eb801b13e73b532688ede2d966e196d2cb314) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie