linux/poky.git/meta/classes, branch danny-next

classes/rootfs_rpm: fix missed complementary packages with complex arch names

2013-02-14T15:19:54+00:00

If the package architecture name is complex (e.g. with the meta-yocto-bsp beagleboard machine and Poky, the architecture-specific package name is "armv7a-vfp-neon"), rpm reports architecture names that contain underscores instead of dashes, which when passed to oe-pkgdata-util during complementary package processing did not match a valid pkginfo path. Replacing the underscores with dashes again fixes the issue. Note that this bug affects the danny branch and not master since the substitution is already performed there in a different manner. Fixes [YOCTO #3792] (From OE-Core rev: e29daf8c3eeb7273e63b6ca6d774b8803880ca46) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

gnomebase: depend on gnome-common-native

2013-02-14T15:19:53+00:00

gnome-common is a build-only dependency so we should depend on the native variant. This also resolves an (incorrect) GPLv3 license issue in gnome-common at build-time. This will also remove the pointless gnome-common-dev RRECOMMENDS in any -dev package that uses gnomebase. (From OE-Core rev: c91b7d06665aa6e44ffce3ea8117cac80cf3446c) Signed-off-by: Ross Burton Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

license.bbclass: Including locale packages

2013-02-14T15:19:52+00:00

As locale packages are installed on the image, we should be including them in the package/license manifest. This ensures that the manifests are accurate and complete. [ YOCTO #2461 ] (From OE-Core rev: f03efceb8a529df944592ff9031639f4e2f7a97d) Signed-off-by: Elizabeth Flanagan Signed-off-by: Richard Purdie

license.bbclass: Avoid grep error message

2013-02-14T15:19:51+00:00

Touch a file that is later greped to make sure it exists. (From OE-Core rev: 178f0d6abfb443ed5d4cc5dab51fc2b78ffade2b) Signed-off-by: Mark Hatle Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

license.bbclass: Collect LICENSE level packages

2013-02-14T15:19:51+00:00

Some bad logic in license.bbclass misses certain package level LICENSEs. (From OE-Core rev: 059dc4ff86d1b1517a53d8f3dc63fe5278751c5d) Signed-off-by: Elizabeth Flanagan Signed-off-by: Richard Purdie

bootimg: Use FAT 32 for images larger than 512MB

2013-01-07T11:32:13+00:00

Fixes [YOCTO #2138] Commit 217584211625b1c496fe5b78aa4765ccf605d2b9 dropped the forced use of FAT32 for the hddimg generation as it broke with very small images (< 32MB). Unfortunately, left to its own devices, mkdosfs appears to select FAT16 even for very large images, resulting in 2.2GB images being generated as FAT16: $ ls -lah core-image-lsb-sdk-atom-pc-20121010233936.hddimg -rw-rw-r-- 1 dvhart dvhart 2.2G 2012-10-17 08:00 core-image-lsb-sdk-atom-pc-20121010233936.hddimg $ file !$ file core-image-lsb-sdk-atom-pc-20121010233936.hddimg core-image-lsb-sdk-atom-pc-20121010233936.hddimg: x86 boot sector, code offset 0x58, OEM-ID "SYSLINUX", sectors/cluster 128, root entries 512, Media descriptor 0xf8, sectors/FAT 138, heads 64, sectors 4502496 (volumes > 32 MB) , serial number 0x50761926, label: "boot ", FAT (16 bit) The result was a runtime boot error from SYSLINUX and a failure to boot live images greater than 1GB in size. While strictly speaking it is the cluster count that determines which FAT size is used, that calculation requires more information than we have readily available (such as sectors per cluster). If we let mkdosfs determine sectors per cluster and just set a sane threshold above which FAT32 is used, we get correct bootable images. With this patch the 2.2GB core-image-lsb-sdk uses FAT32 and the 21 MB core-image-minimal uses FAT16, and both boot in qemu successfully: $ ls -lah tmp/deploy/images/core-image-lsb-sdk-atom-pc-20121212220835.hddimg -rw-r--r-- 1 dvhart dvhart 2.2G 2012-12-12 14:18 tmp/deploy/images/core-image-lsb-sdk-atom-pc-20121212220835.hddimg $ file !$ file tmp/deploy/images/core-image-lsb-sdk-atom-pc-20121212220835.hddimg tmp/deploy/images/core-image-lsb-sdk-atom-pc-20121212220835.hddimg: x86 boot sector, code offset 0x58, OEM-ID "SYSLINUX", sectors/cluster 8, Media descriptor 0xf8, heads 64, sectors 4470304 (volumes > 32 MB) , FAT (32 bit), sectors/FAT 4357, reserved3 0x800000, serial number 0x50c902b7, label: "boot " $ ls -lah tmp/deploy/images/core-image-minimal-atom-pc-20121212220600.hddimg -rw-r--r-- 1 dvhart dvhart 21M 2012-12-12 14:06 tmp/deploy/images/core-image-minimal-atom-pc-20121212220600.hddimg $ file !$ file tmp/deploy/images/core-image-minimal-atom-pc-20121212220600.hddimg tmp/deploy/images/core-image-minimal-atom-pc-20121212220600.hddimg: x86 boot sector, code offset 0x58, OEM-ID "SYSLINUX", sectors/cluster 4, root entries 512, sectors 41408 (volumes <=32 MB) , Media descriptor 0xf8, sectors/FAT 41, heads 64, serial number 0x50c8ffec, label: "boot ", FAT (16 bit) I have tested and booted core-image-minimal and core-image-lsb-sdk for atom-pc with qemu-system-i386 using this patch. (From OE-Core rev: 28d625022d524eb8832f17e221679f68202401a2) Signed-off-by: Darren Hart Cc: Steve Sakoman Cc: Joshua Immanuel Cc: Przemek Czesnowicz Signed-off-by: Richard Purdie

libc-common: Ensure sysconfdir exists before installing files to it

2012-12-13T15:21:45+00:00

Depending on the eglibc configuaration, the directory may or may not exist. (From OE-Core rev: 20e897ca36734cbd77e53e34d9993c941fde1081) Signed-off-by: Richard Purdie

distutils-common-base: Create staticdev pacakge for static libraries

2012-12-13T15:21:44+00:00

(From OE-Core rev: 1a7de9112c8855036f4e07796be18856404eb1c9) Signed-off-by: Stefan Herbrechtsmeier Signed-off-by: Saul Wold Signed-off-by: Richard Purdie

kernel.bbclass: remove explicit version.h target

2012-12-13T15:21:44+00:00

The compilation routine for the kernel has an explicit call to build version.h, which works fine for most kernels, but the location of it has recently changes. commit d183e6f5 [UAPI: Move linux/version.h] commit 10b63956 [UAPI: Plumb the UAPI Kbuilds into the user header installation and checking] moves the file to include/generated/linux/version.h and then to include/generated/uapi/linux/version.h. As a result kernel builds of 3.7 or bisection builds of intermediate kernel commits will fail with: make[2]: *** No rule to make target `include/linux/version.h'. Stop. Making the explicit version.h build conditional on the version, or via a file test would fix the problem, but it introduces some complexity to the build. Even without an explicit call to build version.h, it is always produced by the kernel build, so it can simply be removed. This extra make line was originally so that the kernel version could be determined, so that then different instructions could be executed depending on whether it was a 2.4 or 2.6 kernel. Since we no longer support 2.4, this code is no longer needed. [YOCTO: #3293] (From OE-Core rev: 1ccc1560114d14f7492c034620ad8d7a8d2ef175) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie

kernel-yocto: checkout known branch before leaving do_validate_branches

2012-12-13T15:21:44+00:00

We should always leave the tree on a BSP branch or master when do_validate_branches completes to avoid modifying version tracked files are part of the build process. Modifying these files will lead to errors when changing branches, since the contents would be lost. This is evident in the case that a the meta branch is reset to a known SRCREV and the tree was left on the meta branch. This branch tracks the meta/meta-series, and other artifacts of the original tree construction. When the build process runs, it updates these same files, which creates a conflict when switching branches. This has been fixed in the tree construction scripts to not track these files, but a secondary fix is also required of not leaving the build on these branches, to allow arbitrary trees to be built. [YOCTO #3413] (From OE-Core rev: 36f4e23d037dae758cd42189f2ab00f22a1cd723) Signed-off-by: Bruce Ashfield Signed-off-by: Richard Purdie