linux/poky.git/scripts, branch yocto-1.4

runqemu-internal: Drop distcc support

2013-04-16T11:39:57+00:00

The distcc support is clearly unused and broken, might as well drop the remaining code fragements. (From OE-Core rev: 1a70a3225947aa45f3e1f377d50a5865aac64d2b) Signed-off-by: Richard Purdie

yocto-layer / yocto-bsp: tweak layer.conf comment

2013-04-10T12:04:49+00:00

We have recipes-* directories not a recipes directory; this is left over from the old old layout (2010). (From meta-yocto rev: 8adbbb4b688e60113f68d3974310774686551eff) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

qemu script: explicitly set 32 bit depth for x86-64

2013-04-10T12:00:03+00:00

This patch is the same as 6c22c591374d258228f74814cded34a24b4bf2d3, but for x86-64 targets which exhibit the same problem. Qemu update from 1.2 to 1.4 now allows for 16bit depth in guests, whereby previously only 32bit depth was supported. However, the new support is broken, so we force 32bit depth in all cases. (From OE-Core rev: 6719400533453d0df482ef6e7bb347491e8a3e2b) Signed-off-by: Alexandru DAMIAN Signed-off-by: Richard Purdie

postinst-intercepts, qemu.bbclass: fix segfaults in postinstalls

2013-04-10T11:56:52+00:00

Postinstalls that use qemu are throwing a segmentation fault when building for qemux86-64 on a 64bit host (it might also happen for qemux86 if building on a 32bit host but I didn't test). It looks like qemu looks for ld.so.cache which is not found because it is generated after rootfs_(rpm|ipk|deb)_do_rootfs is called and then it tries to load libraries from the default paths (which are the host's). In order to avoid this, pass the LD_LIBRARY_PATH explicitly to the target's dynamic loader. (From OE-Core rev: 48e8b613b3f5c7b1d917bf3147606d44072ce49e) Signed-off-by: Laurentiu Palcu Signed-off-by: Richard Purdie

qemuimagetest/scenario: Move dmesg to end of test run

2013-04-09T12:25:17+00:00

The dmesg test detects segfaults. This is useful information to have and if one occurs in one of the earlier tests, this can aid debugging. Move the dmesg test to the end of the list of tests so we gain the extra debug info in those cases. (From OE-Core rev: 472dc52974f12c255d9e98e63e82736c7ca2c223) Signed-off-by: Richard Purdie

oe-buildenv-internal: Only add to $PATH if needed

2013-04-09T12:16:53+00:00

First strip $PATH of any existence of the paths needed by Open Embedded and BitBake. Then add the needed paths at the beginning. This makes sure the needed paths are searched first, without growing $PATH unnecessarily if oe-init-build-env is rerun for a directory for which it has previously been run. (From OE-Core rev: 7429db6f38e405774ba66b3fa1bc3ac4b74ae6b9) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

oe-buildenv-internal: Only add to $PATH if needed

2013-04-09T12:16:52+00:00

If $PATH already has the needed paths at the beginning, there is no need to add them again. This allows rerunning oe-init-build-env for the same directory without having $PATH increase unnecessarily every time. (From OE-Core rev: 161abcd3672f83990ede03d67b7388678c07150e) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie

scripts/oe-pkgdata-util: find complementary packages for split packages

2013-04-08T17:02:47+00:00

Check after getting the original package name (e.g. undoing Debian renaming) if there is a complementary package for that name, e.g. if the glob is *-dev, then libudev0 -> libudev -> libudev-dev. Fixes [YOCTO #4136]. (From OE-Core rev: 84a1c6922934a99e8afee0185e58dc4789b54a22) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

qemuimage-tests/sanity/boot: Increase timeout

2013-04-06T16:22:21+00:00

As we've increased the parallelisation on the build servers, we've started to see core-image-minimal sanity test boot failures where the network never comes up. We don't see those failures for core-image-sato, its always minimal. Looking at the results, it can take ~100 seconds for the network to come up, even on the sato images if the machine has a high load. The timeout for the boot test is only 120 seconds compared to 400 on every other test. This change makes the timeout equal for all the tests at 400 seconds in the hope that the load on the autobuilder is causing the sanity tests to run slowly and hence triggering the false negatives. (From OE-Core rev: 331118a253e26821011a31ca9087611ea58a18b8) Signed-off-by: Richard Purdie

oe-setup-builddir: Allow $OECORENOTESCONF to not exist

2013-04-05T22:05:34+00:00

(From OE-Core rev: 6fc14169ac0c3001e3a69eda8d07fc0ac93a15ee) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie