summaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFiles
2011-01-24nfs-utils, e2fsprogs, mtd-utils, libsm: bump PRPaul Eggleton4
This ensures package runtime dependencies are up-to-date after splitting out libuuid and libblkid in util-linux recipe Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Qing He <qing.he@intel.com>
2011-01-24gst-plugins-base: add util-linux to DEPENDSPaul Eggleton1
gst-plugins-base requires libuuid, so add util-linux to DEPENDS. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Qing He <qing.he@intel.com>
2011-01-24util-linux: fix lscpu packagingQing He2
lscpu in util-linux 2.17.2 is specially under GPLv3, ensure it's packaged separately if it's being built. Signed-off-by: Qing He <qing.he@intel.com>
2011-01-24util-linux: fix dangling symlinksQing He2
shutdown and swapon should be in $base_sbindir instead of $sbindir Signed-off-by: Qing He <qing.he@intel.com>
2011-01-24util-linux: separately packaging blkid and uuidQing He2
To avoid full set of util-linux included by library dependencies. Fixes [BUGID #661]. Signed-off-by: Qing He <qing.he@intel.com>
2011-01-24apt: revert the dso_linking_change patch as the new linker fixes itNitin A Kamble2
The newer binutils recipe of version 2.21 has a fix for ld which avoids an issue where weak symbols like pthread_cancel were causing linking to fail wh --no-add-as-needed parameter was passed to ld. See more information here: http://bugs.debian.org/591405 This makes some of the fixes for breakage after gcc dso linking change unnecessary and this is one of them. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-01-24libzypp: revert the dso_linking_change patch as the new linker fixes itNitin A Kamble2
The newer binutils recipe of version 2.21 has a fix for ld which avoids an issue where weak symbols like pthread_cancel were causing linking to fail when --no-add-as-needed parameter was passed to ld. See more information here: http://bugs.debian.org/591405 This makes some of the fixes for breakage after gcc dso linking change unnecessary and this is one of them. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-01-24libmusicbrainz: revert the dso_linking_change patch as the new linker fixes itNitin A Kamble2
The newer binutils recipe of version 2.21 has a fix for ld which avoids an issue where weak symbols like pthread_cancel were causing linking to fail when --no-add-as-needed parameter was passed to ld. See more information here: http://bugs.debian.org/591405 This makes some of the fixes for breakage after gcc dso linking change unnecessary and this is one of them. Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
2011-01-24poky-extract-sdk: allow relative paths for extract-dirScott Garman1
psuedo needs a full path to its pid file, so convert relative extract-dir paths to full ones. The symptom of this bug is receiving the following error: pseudo: Couldn't open relative/path/to/var/pseudo/pseudo.pid: No such file or directory This fixes [BUGID #670] Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-24bitbake/utils: Ignore OSError in unlockfileRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-24Drop remaining bootcdx86 references, the -live images for qemux86 and ↵Richard Purdie10
atom-pc replace this Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21package_deb: Remove access to the D directory which isn't used and might not ↵Richard Purdie1
exist (same problem as the previous patch to package_ipk fixes) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21package_ipk: Do not depend on the existence of "D" to create ipk packageDongxiao Xu1
If build from sstate results, the ${D} will not be installed. In this case the creation of ipk package will be skipped, which will cause the build failure. Fix the issue by removing the judgement of ${D} existence. Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-21glib-2.0: Add missing DEPENDS on dbusRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21dbus: Drop now unneeded DEPENDS on glib-2.0Richard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21util-linux: Drop now unneeded DEPENDS on udevRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21poky-image*-dev: Add -dev Images contianing headers and librariesSaul Wold3
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-21staging: Use relative path in sysroot-destdir for target recipesDongxiao Xu14
Original we used absolute path in sysroot-destdir for both native and target recipes. This commit changes target recipes to use relative path which is same as the image directory. [sgw: merged with libtool sysroot work] Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-21distro tracking: add graphics recipes tracking dataYu Ke1
add required filed for package report system to generate more acurate report Signed-off-by: Yu Ke <ke.yu@intel.com>
2011-01-21README.hardware: add beagleboard documentationDarren Hart1
Document the install and boot process for the Beagleboard xM with provisions for the C4. I need someone with a C4 board to validate the steps. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com> CC: Scott Rifenbark <scott.m.rifenbark@intel.com>
2011-01-21u-boot-omap3: remove in favor of upstream u-bootDarren Hart2
This repository is stale, the u-boot_git.bb recipe uses the upstream repository. Remaining machines using this recipe have already been converted to using u-boot_git.bb. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-21overo: use the new upstream u-boot recipeDarren Hart1
In preparation to remove the u-boot-omap3 recipe, update the overo machine to use the new upstream u-boot recipe. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-21beagleboard: add x-load and u-boot dependsDarren Hart1
The Beagleboard xM requires x-load and u-boot to be installed on the MMC as it has no NAND (as of rev B and onward). Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-21u-boot: Add a new upstream u-boot recipeDarren Hart3
uboot-omap3 appears to be fairly stale (last commit in April 2010) while the upstream u-boot is making regular tagged releases. Add a new recipe using the upstream u-boot repository. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-21x-load: us TI upstream repository, update recipes accordinglyDarren Hart9
TI is now maintaining an upstream x-loader git repository and sakoman will no longer be maintained. Current upstream includes signGP and incorporates it into the Makefile. The new Makefile ift target builds the universal MLO binary. The armv7-a patch is included. Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Tom Zanussi <tom.zanussi@intel.com> CC: Bruce Ashfield <bruce.ashfield@windriver.com>
2011-01-21siggen.py: better print for task hash comparisonKevin Tian1
current bitbake-diffsigs simply print out the whole 'runtaskdeps' when there's mismatch, which is not very readable. On the other hand, 'runtaskhashes' comparison is broken which assumes same key existing in two sides. This commit provides better output by figuring out differences from addition, removal or hash change. Signed-off-by: Kevin Tian <kevin.tian@intel.com>
2011-01-21bitbake.conf: add USERNAME to BB_HASHBASE_WHITELISTKevin Tian1
previously only USER is in the whitelist, however both are possible on different distros Signed-off-by: Kevin Tian <kevin.tian@intel.com>
2011-01-21resolvconf: upgrade to version 1.48Qing He2
from 1.43 Signed-off-by: Qing He <qing.he@intel.com>
2011-01-21zaurusd: upgrade to svn revision 426Qing He3
Signed-off-by: Qing He <qing.he@intel.com>
2011-01-21dbus: upgrade to version 1.4.1Qing He5
from 1.4.0 Signed-off-by: Qing He <qing.he@intel.com>
2011-01-21libnfsidmap: upgrade to version 0.24Qing He3
from 0.23 Signed-off-by: Qing He <qing.he@intel.com>
2011-01-21coreutils: upgrade to version 8.9Qing He2
from 8.5 coreutils now depends on gmp Signed-off-by: Qing He <qing.he@intel.com>
2011-01-21distro-tracking: update some tracking fieldsQing He1
removing some dated items to make the fields more concise. Signed-off-by: Qing He <qing.he@intel.com>
2011-01-21poky-default.inc: bump binutils preferred version to 2.21Scott Garman1
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: fix library RPATHsScott Garman2
This integrates the RPATH fixes we recently applied to libtool. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: Fix QA staging errors for target binutilsScott Garman1
* The spurious paths were caused by a -L on commandline which pointed to build dir. So we dont use -L <wordir> -liberty instead use the libiberty.a directly on commandline effects are same but .la does not have the workdir path in deplibs Patch obtained from OpenEmbedded, written by Khem Raj. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: forward-port the binutils-poison.patchScott Garman2
Update the binutils-poison.patch to apply cleanly on binutils 2.21 Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21binutils: upgrade to 2.21 and add libtool sysroot supportScott Garman18
* Upgraded binutils to v2.21 * Incorporated libtool sysroot patches from OE * Removed patches no longer needed or obsoleted by OE patches Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21insane.bbclass: skip checks on .la installed statusScott Garman1
Enabling libtool sysroot support triggers these errors but they are a valid change in behavior. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21staging.bbclass, utils.bbclass: remove la mangling codeScott Garman2
libtool v2.4 --with-libtool-sysroot eliminates the need for la mangling. Based on Khem Raj's OE commits. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21autotools.bbclass: libtool sysroot support changesScott Garman1
We do not do it for native recipes, as the native compiler should fall back to a prefix of /usr and not solely depend on the sysroot. Otherwise we end up staging everything in the native sysroot before we start to build target recipes. Also remove la mangling code, which is no longer necessary. Commit derived from Khem Raj's OE commits. Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21libtool: fix library RPATHsScott Garman2
Enabling sysroot support exposed a bug where the final library had an RPATH encoded into it which still pointed to the sysroot. This works around the issue until it gets sorted out upstream. Fix suggested by Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21libtool: Changes to enable sysroot supportScott Garman9
* Added OE patches by Khem Raj which enable sysroot support and rename the command line option --with-sysroot to --with-libtool-sysroot to avoid conflicts with binutils and gcc * Removed obsolete cross_compile.patch * Changed SRC_URI_append to SRC_URI += * PR bump for all recipes Signed-off-by: Scott Garman <scott.a.garman@intel.com>
2011-01-21libtool: Move common version specific data to a common include fileRichard Purdie5
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21libtool: Small cleanups of metadataScott Garman3
[based on sections of a patch by Scott Garman extracted by Richard] Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2011-01-21qemu: Upgrade from 0.12.4 to 0.13.0Zhai Edwin24
Patch status: -- Removed -- arm-cp15-fix.patch arm_timer-fix-oneshot-mode.patch arm_timer-reload-timer-when-enabled.patch cursor-shadow-fix.patch -- They are already in upstream or some new changes make them useless. -- Added -- parallel_make.patch: Fix "make -j(>=6)" failure wacom-tablet-fix.patch: Fix seg fault of usb tablet. port92_fix.patch: Fix boot failure on ppc due to port 0x92 conflict. Signed-off-by: Zhai Edwin <edwin.zhai@intel.com>
2011-01-20distrodata.bbclass: add .xz file typeSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2011-01-20meta-environment: Remove the recursive dependency on do_compileDongxiao Xu1
It is not needed to have dependency on each do_compile of its recursive depend tasks. This problem is triggered by building meta-toolchain-sdk from prebuilt result. Some packages like quilt-native, which is already been populated and packaged by do_populate_sysroot_setscene and do_package_write_xxx_setscene, however this recursive dependency of do_compile triggers the tasks flow of "do_setscene --> do_fetch --> do_unpack --> ..." again and do_setscene removes all the quilt-native files, making the other recipes failed while do_patch. Thanks for Kevin's help in root causing this issue. CC: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-20bitbake: fix parameter order for flaglist()Dongxiao Xu1
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
2011-01-20bitbake/providers.py: Fix runtime providers problemsRichard Purdie1
Take a real world testcase where you have two recipes, each of which contains PACKAGES_DYNAMIC = "gdk-pixbuf-loaders-*" and recipes which RDEPEND on some gdk-pixbuf-loaders-xxx package. To select between these you need to set a PREFERRED_PROVIDER. These are specified in the PN namespace so the locgical conclusion is that setting PREFERRED_PROVIDER_gdk-pixbuf = "gtk+" should work. It doesn't and instead checks crazy things. The code was correctly finding the two possible providers, gtk+ and gdk-pixbuf. It was however only accepting PREFERRED_PROVIDER_gtk+ = "gdk-pixbuf" to resolve this problem which reads as the exact opposite to what was wanted. This patch changes the code to do something that makes sense. I suspect that before these changes it was pretty much a null operation rubber stamping the single provider case. For Poky at least it exposes a few cases where -nativesdk recipes were providing the same things as their normal counterparts but these are genuine bugs in the metadata. I've also attempted to make the multiple provider error message human readable as I counldn't understand it and I doubt anyone else could either. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>