linux/poky.git/meta/classes, branch 1.1_M4

cml1/kernel: Update do_menuconfig to use oe.terminal()

2011-09-15T10:23:59+00:00

The recent environment fixes broke the menuconfig task since it couldn't access variables like DISPLAY. This patch updates it to use oe.terminal instead allowing it to work again. (From OE-Core rev: e876a44fa8ed0aa2e09084c1e7ddfc876c3f981b) Signed-off-by: Richard Purdie

package_deb.bbclass, populate_sdk_deb.bbclass: fix meta-toolchain-gmae build

2011-09-15T10:23:56+00:00

[YOCTO #1070] Currently with deb packaging, we have 2 issues when running "bitbake meta-toolchain-gmae". 1) when MACHINE="qemux86", SDKMACHINE="i686", INSTALL_BASEARCH_DEB is "i686", too. This causes the following ERROR: | E: Couldn't find package task-sdk-host-nativesdk NOTE: package meta-toolchain-gmae-1.0-r6: task do_populate_sdk: Failed This is becasue: due to the DPKG_ARCH mapping, we create such a deb package tmp/deploy/deb/i686-nativesdk/task-sdk-host-nativesdk_1.0-r10_i386.deb; dpkg can't recoginze the package. We need to map INSTALL_BASEARCH_DEB in the same way. 2) when MACHINE="qemux86", SDKMACHINE="x86_64", INSTALL_BASEARCH_DEB is "x86_64", too. We get such an ERROR: | E: Couldn't find package task-cross-canadian-i586 NOTE: package meta-toolchain-gmae-1.0-r6: task do_populate_sdk: Failed This is because: dpkg can't recognize the generated package tmp/deploy/deb/x86_64-nativesdk/task-cross-canadian-i586_1.0-r0_i386.deb Here the "i386" suffix is incorrect and should be "x86_64" -- the i386 comes from the line DPKG_ARCH_i586 ?= "i386" in package_deb.bbclass. However, for canadian package, actually here the overriding of DPKG (from "x86-64" to "i386") should not happen -- it accidently happens just because TARGET_ARCH exists in OVERRIDES. We can move the overriding logic to the anonymous python function to work this around. (From OE-Core rev: 63010b9ee89643c8e83656783231f0a7848d9e45) Signed-off-by: Lianhao Lu Signed-off-by: Dexuan Cui Signed-off-by: Richard Purdie

multilib: Remove recipe from multilib.conf that inherits allarch

2011-09-13T16:08:13+00:00

Recipes like update-rc.d and qemu-config inherit "allarch", thus we shouldn't add multilib BBCLASSEXTEND for them in multilib.conf. Besides, we need to add multilib packages as the RPROVIDER contents for those recipes, in order to avoid the NoProvider error when parsing. [YOCTO #1471] (From OE-Core rev: 329d864f9bbf94ad3aae8df43d63fe10e4237e4f) Signed-off-by: Dongxiao Xu Signed-off-by: Richard Purdie

base.bbclass: do not expand PREFERRED_PROVIDER for kernel recipe

2011-09-13T16:08:12+00:00

With Richard's commit f9c36392, we only build one kernel for a system, thus we shouldn't extend PREFERRED_PROVIDER for virtual/kernel. [YOCTO #1471] (From OE-Core rev: 90ad70fe13a9f8409387ca70289998bdca649aeb) Signed-off-by: Dongxiao Xu Signed-off-by: Richard Purdie

imagetest-qemu/runqueue: Since we no longer support BUILDDIR, use TMPDIR

2011-09-09T17:39:26+00:00

Commit 993672fa2739794a6dd0dbd7bb232fa60522b897 removed the BUILDDIR support from runqueue which broke the imagetest-qemu integration. We now therefore need to set TMPDIR and pass this through the environment to ensure the runqueue script finds the right locations without running bitbake directly. This patch also adds a sleep to the qemu command in the error case so that this remains on the screen for a period of time so the user can see errors more easily. This change unbreaks automated testing failures on the autobuilder. (From OE-Core rev: de470333dbdeea444199340e4cd458c13fed6a5a) Signed-off-by: Richard Purdie

terminal.bbclass: Improve environment handling

2011-09-09T17:39:26+00:00

Currently the environment handling for terminals is inconsistent. There are two fixes here: a) Ensure the environment is setup before all oe.terminal call b) Actually set the environment before the spawn calls since we need variables like DISPLAY when the commands are being executed, not just within the terminal environment. If this doesn't happen, DISPLAY can end up not set with the errors that brings with it when trying to run X commands. (From OE-Core rev: 6b680c8da02017bdb17a4826f1819fe0e5f68652) Signed-off-by: Richard Purdie

base.bbclass: fix substring matching in COMMERCIAL_LICENSE

2011-09-08T08:56:31+00:00

Previously, if for example you had a package called "mx", and a second package called "libomxil" listed in COMMERCIAL_LICENSE (without mx being listed there), it would match mx as being commercially licensed because mx is a substring of libomxil. Fix the search to ensure it only matches the listed package name exactly. (From OE-Core rev: b23e51e6c961cf3f7e2aaf89648fecce78424c99) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

useradd.bbclass: use correct value for $D in postinst functions

2011-09-07T22:44:29+00:00

This corrects the location of the password file used during package installation. See http://lists.linuxtogo.org/pipermail/openembedded-core/2011-September/009183.html and subsequent discussion. (From OE-Core rev: 848bb277769af5b094031aeb54d287c158256724) Signed-off-by: Phil Blundell Signed-off-by: Richard Purdie

sstate: Avoid contention between sstate packages

2011-09-07T22:39:59+00:00

If several sstate packages are decompressing at the same time, they can conflict over the "fixmepath". If two packages try to write to this at the same time it results in an error. To avoid this we remove the file once we've finished processing it. (From OE-Core rev: c08d7093bf654ffedb155c5627972e9ecfeb0b60) Signed-off-by: Richard Purdie

sanity.bbclass: re-enable DISTRO check

2011-09-07T21:54:17+00:00

If DISTRO has been specified, ensure it is valid. (Unset or empty string is valid for DISTRO in OE-core by the use of defaultsetup.conf.) (From OE-Core rev: 895aa6b8ee9636a9f9d716c62c0adf951e1ff138) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie