linux/poky.git/meta/classes, branch 1.3_M2

ccache: Ensure CCACHE_DIR is cleaned by do_clean task

2012-07-10T13:25:38+00:00

This ensures a rebuild does really build from scratch when ccache is in use. [YOCTO #2696] (From OE-Core rev: ddf52d0161096b089fad8f3ace69b6515d7b7226) Signed-off-by: Richard Purdie

kernel.bbclass: add non-santized kernel provides

2012-07-09T15:59:00+00:00

If the kernel version string uses characters or symbols that need to be santized for the package name, we can end up with a mismatch between module requirements and what the kernel provides. The kernel version is pulled from utsrelease.h, which contains the exact string that was passed to the kernel build, not one that is santized, this can result in: echo "CONFIG_LOCALVERSION="\"MYVER+snapshot_standard\" >> ${B}/.config % rpm -qp kernel-module-uvesafb-3.4-r0.qemux86.rpm --requires update-modules kernel-3.4.3-MYVER+snapshot_standard % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides kernel-3.4.3-myver+snapshot-standard = 3.4-r0 At rootfs assembly time, we'll have a dependency issue with the kernel providing the santizied string and the modules requiring the utsrelease.h string. To not break existing use cases, we can add a second provides to the kernel packaging with the unsantized version string, and allowing the kernel module packaging to be unchanged. RPROVIDES_kernel-base += "kernel-${KERNEL_VERSION}" % rpm -qp kernel-3.4.3-myver+snapshot-standard-3.4-r0.qemux86.rpm --provides kernel-3.4.3-MYVER+snapshot_standard kernel-3.4.3-myver+snapshot-standard = 3.4-r0 (From OE-Core rev: 7be043178f5b9d16d9a06696bc0b96689f202a8d) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

utils.bbclass: add helper function to add all multilib variants of a specific package

2012-07-09T15:58:58+00:00

This is useful for the scenario where we want to add 'gcc' to the root file system for all multilib variants (From OE-Core rev: 7cd54693363882854cd026ebe071e9f2e03d364e) Signed-off-by: Matthew McClintock Signed-off-by: Richard Purdie

classes/license: fix manifest to work with deb

2012-07-09T15:58:58+00:00

Prepend the license manifest creation call to ROOTFS_POSTPROCESS_COMMAND instead of appending to ROOTFS_POSTINSTALL_COMMAND. The latter is not implemented for the deb backend (and probably ought to just be removed completely), and by using _prepend we can still ensure it occurs before package info is removed (and before buildhistory in case it is needed there in future). (From OE-Core rev: 56fafe083fdb63f156a081344fb1d836e3182bf0) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

sanity.bbclass: the tmpdir can't be longer than 410

2012-07-09T15:58:57+00:00

There will be errors when the length of the tmpdir is longer than 410: 1) Longer than 420: Can't exec "/bin/sh": Argument list too long at /usr/lib/perl/5.10/IO/File.pm line 66. This error happens on both Ubuntu 10.04 and 10.10 when the pkg needs run "autoreconf", this is because it passes many files with absolute path to aclocal, aclocal passes them to perl, this is a limitation of the perl on Ubuntu 10.04 and 10.10, and the perl-native is not ready at this very early stage. 2) Longer than 490: bitbake/lib/bb/persist_data.py", line 197, in connect(database=...) > return sqlite3.connect(database, timeout=5, isolation_level=None) OperationalError: unable to open database file This error happens on Ubuntu 10.04, 10.10 and Fedora 17. This is because the length of the database in sqlite3 module (host's) can't be longer than 490 (or little smaller). The python-native is not ready at this very early stage. The 2 errors are host related, I think that limit the length of the TMPDIR to 410 is OK for most of the build, rarely build sets TMPDIR's longer than 410. [YOCTO #2434] (From OE-Core rev: ebcf949853ff667478a1ea1d3f1f8f41d643e708) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

multilib: Enable multilib remapping for SDK generation

2012-07-09T15:58:54+00:00

Enable the remapping for SDK generation, this is required to be able to create an SDK that targets an alternative multilib. Note, this work does not finish SDK/multilib support, but it is one more step toward making it work properly. (From OE-Core rev: d66d2bdf6214939e8b131f47db2f35d3c64e7dd2) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

package_rpm: Avoid duplicate package generation failures

2012-07-09T10:38:02+00:00

When constructing a multilib based image, it's possible to end up with the same package listed in multiple steps of the install. During resolution we use the --replacepkgs option to avoid errors, as the resulting install solution will be as expected. (We do not enable the replacepkgs option for the final install step, only the generation of the install solution.) (From OE-Core rev: 68ea7d827710ae7c5cf402887d4c12319038e064) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

populate_sdk_rpm: Sync multilib configuration with rootfs_rpm

2012-07-09T10:38:02+00:00

An anonymous python chunk configures some multilib settings for both populate_sdk_rpm and rootfs_rpm. The two classes should contain identical versions to ensure that the generated multilib configuration is the same for the SDK and the rootfs. (From OE-Core rev: 0f60722ef460fa826e4f02e7457004e64ca41d76) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

bootimg: Use STAGING_KERNEL_DIR

2012-07-06T08:39:23+00:00

bootimg.bbclass using STAGING_DIR_HOST/kernel instead of STAGING_KERNEL_DIR, resulting in build failure of live images. | install: cannot stat `/usr/local/dev/yocto/fishriver-test/build/tmp/sysroots/fishriver/kernel/bzImage': No such file or directory Replace it with STAGING_KERNEL_DIR. (From OE-Core rev: 8f16811a8d51982a8b3d70e6087aef4a41926840) Signed-off-by: Darren Hart Tested-by: Tom Zanussi Signed-off-by: Richard Purdie

prexport.bbclass: Fix typo in warning: "AUROPR" -> "AUTOPR".

2012-07-04T16:40:38+00:00

(From OE-Core rev: 0b79c730f3e5c3c5329e439dffd137f2605b6cba) Signed-off-by: Robert P. J. Day Signed-off-by: Richard Purdie