summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* Revert "initrdscripts: fix udevd in the live boot init scripts"Ross Burton2013-01-072-4/+2
| | | | | | | | | | | | | This cherry-pick slipped through testing and lead to unbootable hddimg images. This reverts commit 0140519ba15bfb27ccbfb3d41c7e678a1118fc5c. [ YOCTO #3634 ] (From OE-Core rev: 3fc5923b4c8e99fe22e10fb52181c951330a12f2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bootimg: Use FAT 32 for images larger than 512MBDarren Hart2013-01-071-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <dvhart@linux.intel.com> Cc: Steve Sakoman <steve@sakoman.com> Cc: Joshua Immanuel <josh@hipro.co.in> Cc: Przemek Czesnowicz <przemyslawx.czesnowicz@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sato-icon-theme: fix buildAndreas Müller2012-12-132-3/+3
| | | | | | | | | | | | | | | | | | | | Can't locate XML/Simple.pm in @INC (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at /home/andreas/tmp/oe-core-eglibc/sysroots/x86_64-linux/usr/lib/icon-naming-utils/icon-name-mapping line 12. | BEGIN failed--compilation aborted at /home/andreas/tmp/oe-core-eglibc/sysroots/x86_64-linux/usr/lib/icon-naming-utils/icon-name-mapping line 12. | make[3]: *** [install-data-local] Error 2 | make[3]: Leaving directory `/home/andreas/tmp/oe-core-eglibc/work/all-angstrom-linux/sato-icon-theme-0.4.1-r5/sato-icon-theme-0.4.1/16x16/actions' | make[2]: *** [install-am] Error 2 | make[2]: Leaving directory `/home/andreas/tmp/oe-core-eglibc/work/all-angstrom-linux/sato-icon-theme-0.4.1-r5/sato-icon-theme-0.4.1/16x16/actions' | make[1]: *** [install-recursive] Error 1 | make[1]: Leaving directory `/home/andreas/tmp/oe-core-eglibc/work/all-angstrom-linux/sato-icon-theme-0.4.1-r5/sato-icon-theme-0.4.1/16x16' | make: *** [install-recursive] Error 1 | ERROR: oe_runmake failed | ERROR: Function failed: do_install (see /home/andreas/tmp/oe-core-eglibc/work/all-angstrom-linux/sato-icon-theme-0.4.1-r5/temp/log.do_install.21502 for further information) (From OE-Core rev: 8e057a58769000dfa16c77ba4555f6e169f0298b) Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libc-common: Ensure sysconfdir exists before installing files to itRichard Purdie2012-12-131-0/+1
| | | | | | | | Depending on the eglibc configuaration, the directory may or may not exist. (From OE-Core rev: 20e897ca36734cbd77e53e34d9993c941fde1081) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pulseaudio: explicitly set --with-database=simpleMario Domenech Goulart2012-12-132-1/+2
| | | | | | | | | | | | | | The default value for --with-database is "auto". So, if some package installs a database library and pulseaudio auto detects, that library will be added to the dependencies list, causing a dependency error at do_rootfs time. For example, samba installs libtdb, which is one of the pulseaudio supported databases. (From OE-Core rev: 400ebfde27a2de4014d4711ac80a87116ad17e55) Signed-off-by: Mario Domenech Goulart <mario@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* distutils-common-base: Create staticdev pacakge for static librariesStefan Herbrechtsmeier2012-12-131-1/+4
| | | | | | | | (From OE-Core rev: 1a7de9112c8855036f4e07796be18856404eb1c9) Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: remove explicit version.h targetBruce Ashfield2012-12-131-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-yocto: checkout known branch before leaving do_validate_branchesBruce Ashfield2012-12-131-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | 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 <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autogen: use pkg-config directly instead of guile-configRoss Burton2012-12-132-2/+180
| | | | | | | | | | | | | | | | | | The autoconf macros in autogen use dpkg (!) and guile-config to determine what/where Guile is. If the build host has an installed guile, these can produce conflicting results. More interestingly, if the Guile library source and compiled form have bad timestamps (source newer than compiled) the configure scripts knows that Guile is present but doesn't know what version it is, resulting in compile errors. [ YOCTO #3370 (partially) ] (From OE-Core rev: 29f37af146b50fa39021884ef97bca9711ee924b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* guile: touch compiled modules on sstate installRoss Burton2012-12-131-1/+12
| | | | | | | | | | | | | | | | | | | | | | | | When guile is installed from sstate, if the compiled files get a modified time older than the source files then guile will produce warnings like this: ;;; note: source file /data/poky-master/tmp/sysroots/x86_64-linux/usr/share/guile/2.0/ice-9/boot-9.scm ;;; newer than compiled /data/poky-master/tmp/sysroots/x86_64-linux/usr/lib/guile/2.0/ccache/ice-9/boot-9.go Not staging the files and letting guile re-compile them on demand won't work: ;;; compiling /data/poky-master/tmp/sysroots/x86_64-linux/usr/share/guile/2.0/system/base/compile.scm ;;; it seems /data/poky-master/tmp/sysroots/x86_64-linux/usr/share/guile/2.0/system/base/compile.scm ;;; is part of the compiler; skipping auto-compilation So, use a sstate postinst function to explicitly touch the compiled files after the extraction to ensure that they are fresher. [ YOCTO #3370 ] (From OE-Core rev: 1e96fea6c603a500e21b9cd4626ecd19049bf04b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* guile: fix bashism in scriptRoss Burton2012-12-131-2/+4
| | | | | | | (From OE-Core rev: e206443c132ee94227580fad16b16332007aec42) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rsync doesn't create hardlinks for certain filesAmy Fong2012-12-131-0/+6
| | | | | | | | | | | | | | | | | | | commit 4205a4c5d959643cf6c186e0939e202fb6006b82 Author: Amy Fong <Amy.Fong@windriver.com> Date: Thu Nov 29 09:21:49 2012 -0500 rsync cannot create hardlink for node file when use option --link-dest=DIR. By default, rsync's configure file disables certain capabilities when crosscompiling. Signed-off-by: Amy Fong <Amy.Fong@windriver.com> (From OE-Core rev: 4e6b3eeb7cf2ea002819daa57a1248de2daac0cd) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* squashfs: fix for CVE-2012-4024yanjun.zhu2012-12-132-0/+75
| | | | | | | | | | | | | | | | | | | | Reference:http://squashfs.git.sourceforge.net/git/gitweb.cgi?p= squashfs/squashfs;a=commit;h=19c38fba0be1ce949ab44310d7f49887576cc123 Fix potential stack overflow in get_component() where an individual pathname component in an extract file (specified on the command line or in an extract file) could exceed the 1024 byte sized targname allocated on the stack. Fix by dynamically allocating targname rather than storing it as a fixed size on the stack. [YOCTO #3513] (From OE-Core rev: a45ec682748b0d6e5bb21af04d205edb5ef1360e) Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libproxy: Fix for CVE-2012-4504yanjun.zhu2012-12-132-0/+30
| | | | | | | | | | | | | | | | | Reference:https://code.google.com/p/libproxy/source/detail?r=853 Stack-based buffer overflow in the url::get_pac function in url.cpp in libproxy 0.4.x before 0.4.9 allows remote servers to have an unspecified impact via a large proxy.pac file. http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-4504 [YOCTO #3487] (From OE-Core rev: a1ef9a5f647abfafd337b22b6353848962bcb00d) Signed-off-by: yanjun.zhu <yanjun.zhu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pulseaudio: explicitly disable xen, rather than letting it detectGilbert Coville2012-12-132-1/+2
| | | | | | | (From OE-Core rev: 3b7a39d5e386f5e5b098b532d70c32d611a47ac9) Signed-off-by: Gilbert Coville <gilbert_coville@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcgroup: Use BPN in SRC_URIRichard Purdie2012-12-131-1/+1
| | | | | | | | | | | If we don't do this, multilib and other varients using BBCLASSEXTEND will fail. (this patch is a subset of 9a97367038a1e2431bf94211dabbc5aedbbee3bb - Ross Burton) (From OE-Core rev: da81f2816086c240ad5ebf74f3b8a2caed0b6cae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: udev: Handle alternative binary pathsOtavio Salvador2012-12-132-6/+21
| | | | | | | | | | | This allows use of udev daemon for different installation destinations so allowing use of udev's from systemd code for initramfs. (From OE-Core rev: dcf95bed1d9152d9cdb908b4e131e1c7c46cec84) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initrdscripts: fix udevd in the live boot init scriptsRoss Burton2012-12-134-5/+9
| | | | | | | | | | | | | | | udevd moved location and isn't in $PATH anymore, so use an absolute path to start it. The control socket path moved too, so mkdir the directory it's in. Mounts the new devtmpfs on /dev device tree. (From OE-Core rev: 75f28875bcae2f91437d89d1ad97df29226e3303) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Alexandru Damian <alexandru.damian@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* initramfs-framework: init: Stop mount warnings during bootOtavio Salvador2012-12-131-2/+5
| | | | | | | | | | For a completely quiet boot using recent versions of utilities, the /etc/fstab and /var/lock need to be available. (From OE-Core rev: 49434f789a772620a8eae7220812296523616956) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* buildhistory.bbclass: Fix hostname print for 'No changes' caseOtavio Salvador2012-12-131-1/+1
| | | | | | | | (From OE-Core rev: 0acd5a16a874b438eb288292833080bac9f9ea8b) Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: remove unused lttng-syscalls patchTom Zanussi2012-12-131-41/+0
| | | | | | | | | | | | commit b7e184508 (lttng-2.0: fix srcrev/pv to match the recipe filenames) removed the lttng-sycalls-protect-is_compat_task-from-redefiniti.patch from the SRC_URI but forgot to remove the patch itself. (From OE-Core rev: 47df8cbb6eb757a439d3d9f44e2615faa74fd258) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-2.0: fix srcrev/pv to match the recipe filenamesChristopher Larson2012-12-133-8/+7
| | | | | | | | | | | Somehow the recipe names got bumped, but the SRCREV and PVs in the recipes didn't get updated, so they were still building old versions. (From OE-Core rev: 29668e3698251c032e9d1b7d69370c11dd6b3c64) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-tools-profile: replace 'legacy' lttng with lttng 2.0Tom Zanussi2012-12-131-4/+21
| | | | | | | | | | | | | | packagegroup-core-tools-profile currently pulls in the 'legacy' lttng packages, which are useless without legacy lttng support in the kernel. This makes packagegroup-core-tools-profile pull in the lttng 2.0 packages instead, which don't need any kernel modifications to work. (From OE-Core rev: 6b196f4b7feca7caa5d2a09c0e4d6a2c57df6cd3) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: bump SRCREV to latestMartin Jansa2012-12-131-1/+1
| | | | | | | (From OE-Core rev: d18bb4731898b3a9bb35a8d794d67e15e636dc02) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pulse: fix Bashism in string testSaul Wold2012-12-132-2/+2
| | | | | | | (From OE-Core rev: daba8aabaea5d16becd06b8b0639a34c3158d855) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kmod: fix git repo URLEric Bénard2012-12-131-1/+1
| | | | | | | (From OE-Core rev: d56e4f19559c4389f3ced2ebe53ea4f49c8969b0) Signed-off-by: Eric Bénard <eric@eukrea.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image.bb: Bump SRCREV for 1.3_M5.rc41.3_M5.rc4Elizabeth Flanagan2012-10-101-1/+1
| | | | | | Bumping the SRCREV for danny in preparation for 1.3_M5.rc4 Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
* gdbm: Resolve host contamination issueRichard Purdie2012-10-101-0/+3
| | | | | | | | | | | | | | | | | | The autoconf macros detect the presence of -ldbm or -lndbm on the host system and add the library to link against, for now good reason I can explain. This patch makes the build behave determinstically whether they're present or not. Other than the extra linkage, there doesn't appear to be any other change in behaviour from these options and they look like dead code. The extra linkage can cause problems where sstate is used on a machine where the extra librbary isn't present causing build failures. (From OE-Core rev: f609bf5525450bfdb8e0864d44c41cce7f9319c9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image.bb: Bump SRCREV for 1.3_M5.rc4Elizabeth Flanagan2012-10-101-1/+1
| | | | | | Bumping the SRCREV for danny in preparation for 1.3_M5.rc4 Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
* Revert "build-appliance-image.bb: Bumping SRCREV for 1.3_M4"Elizabeth Flanagan2012-10-101-1/+1
| | | | | | Wrong build number in the commit log This reverts commit c030e463abf4940186df49394e2414e856d4b381.
* build-appliance-image.bb: Bumping SRCREV for 1.3_M4Elizabeth Flanagan2012-10-101-1/+1
| | | | | | In preparation for 1.3_M4, bumping SRCREV for the build appliance Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
* pkgconfig: Drop the RREPLACES for pkgconfig-devRichard Purdie2012-10-102-2/+1
| | | | | | | | | | | | | | | This line causes pkgconfig-dev to replace pkgconfig so the package with all the files in is replaced by one with no files. This makes no sense and hence we should just remove this broken line. At this point in the release, this is the safest way to fix this even if an empty -dev package is left available. [YOCTO #2878] (From OE-Core rev: 5bed2bb831b379a8fbf2f725435af4b7c934359e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc: force make to use /bin/bashSaul Wold2012-10-102-1/+6
| | | | | | | | | | | | | | | | | | | | | The eglibc core build still has a number of issues with /bin/dash. Recently found is both sysdeps/unix/make-syscalls.sh and it's output, which make calls via SHELL do not play well with /bin/dash. By force make to use /bin/bash via SHELL setting it works correctly. Currenly known issues are: make-syscalls.sh line with a bad substitution, which can be corrected by: vdso_symver="$(printf '%s\n' ${vdso_symver} | sed 's/\./_/')" Following that there is an issue with emiting a '\n' through a second echo and then to the compiler. There maybe more issues beyond that. [YOCTO #3080] (From OE-Core rev: 9d002f7cdc5309c4d850a76e4fd73ff04c980a07) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: add archlib_exp variable used to generate ARCHLIB_EXP in config.hTom Zanussi2012-10-103-1/+43
| | | | | | | | | | | | | | | | | | | | | | | | | | | | perl.c uses an ARCHLIB_EXP define to generate compile-time code that adds the archlibexp path to @INC during run-time initialization of a new perl interpreter. Because we've changed this value in a temporary way to make it possible to use ExtUtils::Embed in the target build (the temporary value in config.sh gets re-stripped out during packaging), the ARCHLIB_EXP value that gets generated still uses the temporary version instead of the original expected version (i.e. becauses it's in the generated config.h, it doesn't get stripped out during packaging like the others in config.sh). This creates an unmodified version called archlib_exp that gets used by a modified config_h.SH to get the correct value into config.h This patch uses an unmodified version of archlibexp called archlib_exp, introduced to config.sh, which is used to generate the correct value of ARCHLIB_EXP into config.h Fixes [YOCTO #3099]. (From OE-Core rev: cbcfdeb1d55e2e76f199750bda401bad126ae234) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bzip license: bzip2 not bzip.Flanagan, Elizabeth2012-10-101-0/+0
| | | | | | | | | | The name of the license for bzip2 is wrong causing warnings to be thrown. (From OE-Core rev: 566c6101cc7a8d90973eb22478ffc77eac23f81c) Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-cross-canadian: Fix gettext dependencyRichard Purdie2012-10-101-1/+1
| | | | | | | | | | | There was a problem in commit ad23395cd1f6c0cbfcc6980b6071d589f9f6cde0 since gettext-nativesdk was translated to gettext instead of nativesdk-gettext. This fixes to use the correct dependency. (From OE-Core rev: a6e325342cb489e05927d6cb2bb0a24fa6c20ef8) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: perf: parallel build and tools fixesBruce Ashfield2012-10-103-10/+10
| | | | | | | | | | | | | | | | | | | | | | korg commit 42dcd1f4e [perf tools: Fix parallel build] fixes parallel build issues that are being seen in the autobuilder. We also have a fix from Tom: [ perf annotate: replace 'expand' with equivalent sed expression We don't have 'expand' in our userspace so we need to accomplish the same thing using 'sed', which we do have. ] So we apply it to all BSP branches and kernel types. (From OE-Core rev: f06e7d38db35c56c71a42264361ec45fb3777a14) Signed-off-by: Tom Zanussi <tom.zanussi@intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Also add datadir/sgl to sstate whitelist to avoid openjade warningRichard Purdie2012-10-101-1/+1
| | | | | | (From OE-Core rev: e0ff54db5a5ab171ee1d0dbcf7f267235c21e601) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: When applying qemu-mips workaround, check the file exists firstRichard Purdie2012-10-101-2/+4
| | | | | | | | | If qemu-mips was disabled as done in some distros, this wrapper would fail. Therefore check if the file exists before wrapping it. (From OE-Core rev: 9ec1c06915b10d142bf5646396c4e91bb61a40a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto-tiny: Add tiny recipe for the 3.4 linux-yocto kernelDarren Hart2012-10-101-0/+27
| | | | | | | | | | | | | | | This recipe builds the "tiny" kernel type defined by the linux-yocto meta-data. Support is defined for the qemux86 machine via common-pc-tiny.scc in the linux-yocto meta branch. The resulting kernel is 1.8 MB and boots to a serial console with with qemux86 and core-image-minimal using the following command: qemu -kernel tmp/deploy/images/bzImage-qemux86.bin -initrd tmp/deploy/images/core-image-minimal-qemux86.cpio.gz -append "root=/dev/ram0 console=ttyS0" -nographic (From OE-Core rev: cf25f211ec420e1e8dd48c8e62f60deefe2c6d53) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nfs-export-root: add explict no_subtree-check to suppress warningSaul Wold2012-10-102-1/+3
| | | | | | | | | | | exportfs: /etc/exports [1]: Neither 'subtree_check' or 'no_subtree_check' specified for export "*:/". Assuming default behaviour ('no_subtree_check'). NOTE: this default has changed since nfs-utils version 1.0.x (From OE-Core rev: 1438228d3b54dfdcf8c36154c927c80fcecf688e) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: tiny: Add qemu KMACHINE to common-pc-tiny.sccBruce Ashfield2012-10-101-1/+1
| | | | | | | | | | | | | Updating the meta SRCREV to pickup the following change: Ensure the qemux86 machine is defined in common-pc-tiny as it is for -standard and -rt. (From OE-Core rev: 1076910ac3cd55a3f87b5ca7a1db1e38c623480a) Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.4: fix kconfig warnings and unnecessary optionsBruce Ashfield2012-10-101-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Updating the kernel configuration fragments to fix the following issues: - remove options that are no longer in the 3.4 kernel - disable unused, but large kernel modules - fix kconfig audit warnings for x86 BSPs - make uprobes reusable by multiple fragments The following meta branch commits are represented by this update: 3da1172 uprobes: split into enable and patch fragments 17ec51a meta: cleanup invalid/obselete 3.4 CONFIG options b5cee42 meta: disable OCFS2 by default efe937e meta: drm: tag DRM options as 'hardware' 10b5155 meta: emenlow: clean emenlow configuration warnings a907b82 meta: add CONFIG_SHMEM to standard kernel config (From OE-Core rev: a01bb3ec72c375c0f06006769969f63fed3ef566) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pulseaudio: ensure X11 and consolekit are disabledSaul Wold2012-10-102-4/+5
| | | | | | | | | | | | | | When DISTRO_FEATURES does not include X11 ensure that both x11 and gtk are diabled correctly. ConsoleKit also has x11, so ensure that any RDEPENDS is also excluded. The flags for x11 changed at somepoint to use enable/disable, but this recipe was not updated. (From OE-Core rev: 0730d3449aa28600488e73de883240ba2bd60aec) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* package_rpm.bbclass: Fix an issue where complementary installs failMark Hatle2012-10-101-5/+9
| | | | | | | | | | | | | | | | Also ensure that we always cleanup the temporary install manifest files, some of them will cause problems if they exist in multiple install attempts. Finally verify that the lists remain uniquely sorted otherwise the complementary install may install the same files numerous times, triggering a failure. (From OE-Core rev: 4f2a290cbcc6c21afbb2a6e6148efdef4d135b41) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Add extra entries to the sstate duplicate files whitelistRichard Purdie2012-10-101-2/+8
| | | | | | | | | | | | | | This avoids errors where gcc/binutils get installed to the native sysroot in the same location for multiple package architectures. Ultimately making these native recipes with ${PACKAGE_ARCH} appended to PN will resolve this but hide the warnings until this gets sorted out. Also hide the python and docbook catalog warnings since they're known about, nothing to worry about and we'll aim to clean them up properly in the 1.4 cycle. (From OE-Core rev: 5bae58a5b59c04d8947f4842f19837a914c29b52) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Normalise paths before comparing with the whitelistRichard Purdie2012-10-101-0/+1
| | | | | | | | | Without this, path components like // could break comparisions with the whitelist leading to warnings being displayed to the user unintentionally. (From OE-Core rev: d3c46ca56fab2f07bf16b61514f30765543a8747) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdrm: Explicitly disable the cairo dependencyRichard Purdie2012-10-103-0/+42
| | | | | | | | | | We don't want the cairo dependency. Unfortunately simply checking whether its present isn't good enough. If its not in DEPENDS, it can disappear half way through building. We therefore need to explictly disable it. (From OE-Core rev: 51df11c5747f69b4112121df78fc1e10644d390a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* toolchain-scripts.bbclass: Export M4Khem Raj2012-10-101-0/+1
| | | | | | | | | | | some packages use M4 variable from environment and sometimes its hardcoded to /usr/bin/m4 if not found in environment. Lets define it such that it is picked from path (From OE-Core rev: 06c5593d15f206458b9a5b45ed1229abfee16e95) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cross-canadian.bbclass: add native chrpath dependencyLaurentiu Palcu2012-10-101-0/+7
| | | | | | | | | | | | | In order for the RPATHs in 32bit toolchain binaries to be relocated properly, chrpath >=0.14 is needed. [YOCTO #3161] [YOCTO #3201] (From OE-Core rev: 71c71b972100803d33fbb062a237e8a15167387b) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>