summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* create-pull-request: allow '+' in git PROTO_RE, ie for 'git+ssh://'Martin Jansa2011-06-011-1/+1
| | | | Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* busybox: sync do_install() with oe master (mostly)Phil Blundell2011-06-012-48/+57
| | | | | | | | | | | | | This is basically a backport of the current state of the art from the openembedded master repo. In particular this fixes an installation error on micro: | + cp -dPr /home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/bin /home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/sbin /home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image /home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/busybox/ | cp: will not create hard link `/home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/busybox/image/bin' to directory `/home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/busybox/bin' | cp: cannot copy a directory, `/home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image', into itself, `/home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/image/busybox/image' | ERROR: Function 'do_install' failed (see /home/pb/oe/build-meta/tmp-eglibc/work/i586-oe-linux/busybox-1.18.4-r1.2/temp/log.do_install.3808 for further information) Signed-off-by: Phil Blundell <philb@gnu.org>
* sudo.inc: Add do_install_prepend () to sudo.incXiaofeng Yan2011-06-011-0/+12
| | | | | | | | | | Fix bug [YOCTO #1092] Own a directory "/var/lib" before do_install() because if there isn't this directory during installing, \ then script "mkinstalldirs" from "sudo package" will create directory "/var/lib/sudo" by recursion with mode "0700" \ which will cause bug [YOCTO #1092]. So I add do_install_prepend() to create a "/var/lib" which can be accessed \ by common user before installing files. Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
* distro tracking: updatesSaul Wold2011-06-011-27/+72
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gnutls: update to 2.12.5Saul Wold2011-06-017-79/+79
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* rxvt-unicode: update to 9.11Saul Wold2011-06-014-0/+0
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* qmmp: update to 0.5.1Saul Wold2011-06-011-2/+3
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* alsa-tools: update to 1.0.24.1Saul Wold2011-06-011-0/+0
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gthumb: update to 2.12.3Saul Wold2011-06-011-2/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* msmtp: update tof 1.4.24Saul Wold2011-06-011-2/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* mc: update to 4.7.5.2Saul Wold2011-06-011-2/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* mailx: update to 12.5Saul Wold2011-06-011-6/+7
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* chkconfig: update to 1.3.52Saul Wold2011-06-011-2/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* update-alternatives-dpkg update to 1.16.0.3Saul Wold2011-06-011-0/+0
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* dtc: Cleanup and update recipeSaul Wold2011-06-016-20/+21
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gobject-introspection: Update to 0.10.8 GitSaul Wold2011-06-013-2/+6
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* gettext: Update to 0.18.1.1Saul Wold2011-06-0117-105/+107
| | | | | | Add Upstream Status tags to patches Signed-off-by: Saul Wold <sgw@linux.intel.com>
* glew: update to 1.6.0Saul Wold2011-06-012-2/+5
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* util-linux: update to 2.19.1Saul Wold2011-06-0110-10/+7
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* newt: add Upstream-StatusSaul Wold2011-06-011-0/+3
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* mpeg2dev: add Upstream-StatusSaul Wold2011-06-011-0/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* libmad: add Upstream-StatusSaul Wold2011-06-013-0/+6
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* tzdata: update to 2011gSaul Wold2011-06-011-2/+2
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* sysstat: update to 10.0.0Saul Wold2011-06-012-10/+10
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* less: update to 443Saul Wold2011-06-011-3/+3
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* allarch.bbclass: A "all" TARGET_ARCH is dangerous as an OVERRIDERichard Purdie2011-06-011-1/+1
| | | | | | | | | Having a generic word like "all" as an override is dangerous as this is an override and can cause issues for function names like "sysroot_stage_all". This patch changes it to "allarch" to help avoid this kind of problem. The field is only used in the name of directories anyway. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Improve handling of 'all' architecture recipes and their interaction with sstateRichard Purdie2011-05-3113-25/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The existing PACKAGE_ARCH = "all" mechanism of sharing packages is problematic with sstate since there are a variety of variables which have target specific values and the sstate package therefore correctly changes signature depending on the MACHINE setting. This patch creates a new "allarch" class which sets: PACKAGE_ARCH = "all" (as per the existing convention) INHIBIT_DEFAULT_DEPS = "1" (since its not target specific and therefore can't depend on the cross compiler or target libc) TARGET_ARCH = "all" TARGET_OS = "linux" TARGET_CC_ARCH = "none" (since these variables shouldn't change between the different packages and target compiler flags shouldn't be getting used) PACKAGE_EXTRA_ARCHS = "" (since we shouldn't be depending on any architecture specific package architectures) Not all PACKAGE_ARCH = "all" recipes can use this class since some run configure checks on the compiler. This means they have target specific components and therefore the "all" classification is incorrect. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* prelink: remove dependency on transfig-nativePhil Blundell2011-05-311-1/+2
| | | | | | | Per http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003179.html Signed-off-by: Phil Blundell <philb@gnu.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: make pidof usuable in a standalone settingKoen Kooi2011-05-311-2/+4
| | | | | | | | | | | | Currently it's a symlink to killall5: $ dpkg-deb -c sysvinit-pidof_2.88dsf-r1_armv7a.ipk | grep pidof lrwxrwxrwx root/root 0 2011-05-27 11:05 ./bin/pidof.sysvinit -> /sbin/killall5 The point of the pidof subpackage was to have a pidof without needing sysvinit, this restores that behaviour. Signed-off-by: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto: update meta SRCREVBruce Ashfield2011-05-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes [YOCTO: 1111] and updates the meta branch with some cleanups and feature groupings. From the meta branch itself: 06d3793 meta: add romley features f101ab9 meta: remove 'not set' lines from netfilter.cfg d0599f8 meta: add dca feature 0cd5ef1 meta: replace open-coded E1XXXX options with intel-e1xxxx feature 3f88c17 meta: add intel-e1xxxx feature f7537af meta: replace open-coded igb options with igb feature f72e046 meta: add igb feature 989cd7d meta: add ixgbe feature 8543f7d meta: replace open-coded dma engine options with dmaengine feature 8fc67cd meta: add dmaengine feature 610e419 meta: add hugetlb feature ac22176 meta: add uio feature ce14a0d meta: replace open-coded hpet options with hpet feature 6a30aaa meta: add hpet feature 0ae7362 routerstationpro: watchdog config Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
* bitbake.conf: make OVERRIDES match what people expectKoen Kooi2011-05-301-6/+6
| | | | | | | | In the current situation TARGET_ARCH will override MACHINE, which is counter intuitive since the machine is more specific than the arch. The order is now pn-$PN} -> arch -> machine -> distro as the machine is a set of defaults and the distro is the ultimate policy. 'failfast' has been removed since it's not used anymore, just like 'local'
* gcc-cross-csl-2008q1: Drop last remaining fail-fast override use and make it ↵Richard Purdie2011-05-301-1/+1
| | | | | | unconditional Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* site/powerpc-common: remove the incorrect dlopen default settingYu Ke2011-05-301-2/+0
| | | | | | | | | | | | | | | These two setting for dlopen is not correct. dlopen is not available in libc, instead it is provided by libdl. so the setting should not be "yes" by default. This fixes [YOCTO #736] [YOCTO #737] Thanks Richard for pointing out the root cause. CC: Richard Purdie <richard.purdie@linuxfoundation.org> CC: Philip Balister <philip@balister.org> CC: Koen Kooi <koen@dominion.thruhere.net> Signed-off-by: Yu Ke <ke.yu@intel.com>
* package.bbclass,prserv.bbclass: Compare USE_PR_SERV with "1" or "0"Khem Raj2011-05-292-2/+2
| | | | | | | | | Value of USE_PR_SERV is either "1" or "0" looking at settings in bitbake.conf USE_PR_SERV = "${@[1,0][(bb.data.getVar('PRSERV_HOST',d,1) is None) or (bb.data.getVar('PRSERV_PORT',d,1) is None)]}" So we compare the strings Signed-off-by: Khem Raj <raj.khem@gmail.com>
* uclibc: Add disabled COMPILE_IN_THUMB_MODE to uClibc.machine for all ARM ↵Khem Raj2011-05-294-0/+4
| | | | | | | | | configurations This entry need to exist so that it can be manipulated later to decide if uclibc is to be compiled in thumb mode or arm mode Signed-off-by: Khem Raj <raj.khem@gmail.com>
* license.bbclass: Infinite recursion of or nodesBeth Flanagan2011-05-291-7/+8
| | | | | | | | | | This fixes two bugs. When populate_lic was hitting | it was going into an infinite recursion of the node. Also, some LICENSE fields may start with "(". We want to avoid invalid python syntax here, so we strip out the whitespace. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
* license.bbclass: Sane Parsing of licensesBeth Flanagan2011-05-271-38/+114
| | | | | | | | | | | | | | | | | | | | | This is a first pass at sane license parsing, using python abstract syntax trees. A few notes on this since ast is not generally used. I massage the LICENSE field to be more pythonesque and then create an ast. I then dump the ast and using a LicenseVisitor class, recurse through the tree, looking for licenses. I then copy and link. It's cleaner, allows for easier addition of logic and while it takes slightly more CPU, it's also slightly faster in initial small scale tests. It doesn't recognize the '+' or '*' modifiers to the licenses yet nor does it know what to do with bitors (|), since I'm not even sure what to do with them. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
* uclibc_git.bb: Fix patch path in SRC_URIKhem Raj2011-05-271-1/+1
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* gupnp-tools: Add gupnp-av to DEPENDSSaul Wold2011-05-271-1/+1
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* License Field Cleanup: Non-standard field namesBeth Flanagan2011-05-2738-38/+38
| | | | | | | | | | | | I've cleaned up some odd license fields, fixed some license names and corrected some incorrect licenses. LICENSE really needs a pass through by the maintainers as some of the licensing is incorrect. Also, every license with Artistic should be gone through and noted as which version of Artistic. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
* common-licenses: Adding new licenses and renamingBeth Flanagan2011-05-27126-2599/+21995
| | | | | | | | | | | | | | I'm adding full common licenses to the common license directory. These licenses are taken from the SPDX project or the OSI license repository. They conform to the SPDX naming convention and will be used by the new license.bbclass license parser in order to maintain some sort of internal standard for license naming. Going forward, we should have a bigger conversation about the LICENSE field and standardizing that to conform to this naming standard. Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com>
* classes/package_xxx.class: Use PKGE/PKGV/PKGR.Lianhao Lu2011-05-274-17/+17
| | | | | | Use PKGE/PKGV/PKGR to build various package feed in tasks of pacakge_write_xxx. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* classes/package(prserv).bbclass: Get PRAUTO and use PKGV/PKGR.Lianhao Lu2011-05-272-15/+65
| | | | | | | | | | | 1. Added package_get_auto_pr to PACKAGEFUNCS to get the auto incremented value(PRAUTO) from remote PR service. 2. use PKGV/PKGR for pkgdata which will be used by package_write_xxx. 3. Added supporting functions in prserv.bbclass. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
* conf/bitbake.conf: Added variables for PR service.Lianhao Lu2011-05-277-10/+22
| | | | | | | | | | | | | | | | | | | | Added following variables for PR service: USE_PR_SERV: flag of whether to use the network PR service PRAUTOINX: search index for the network PR service PKGE/PKGV/PKGR: epoch, version and revision used in package feed. EXTENDPKGV: full package version string used in package relationships. For the following recipes, replace EXTENDPV with EXTENDPKGV: udev, xcb, xorg-proto, util-macros and linux-libc-headers then removed the unused EXTENDPV and EXTENDPEVER variables Users should use EXTENDPKGV instead for package feed generation. Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* shared-mime-info_0.90.bb: Fix more parallel build issuesKhem Raj2011-05-272-2/+29
| | | | | | | | While building for beagleboard with -j4 I ended up failures in generating and checking xml files. This is a backport from upstream that fixes the issue. Signed-off-by: Khem Raj <raj.khem@gmail.com>
* uclibc.inc: Set COMPILE_IN_THUMB_MODE in .config if ARM_INSTRUCTION_SET != armKhem Raj2011-05-271-0/+1
| | | | | | This will configure uclibc to be compiled in thumb/thumb2 mode Signed-off-by: Khem Raj <raj.khem@gmail.com>
* uclibc_git.bb: Fix compilation on arm when using thumb instruction setKhem Raj2011-05-273-1/+57
| | | | Signed-off-by: Khem Raj <raj.khem@gmail.com>
* utils.bbclass: make FILESEXTRAPATHS colon delimitedDarren Hart2011-05-271-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes [YOCTO 1102] Path variables are typically : delimited. White space is allowed in paths, so is not a good choice for separating paths. Currently utils.bbclass performs the following: extrapaths = (bb.data.getVar("FILESEXTRAPATHS", d, True) or "").split() This splits FILESEXTRAPATHS on whitespace. It later splits overrides on : and reassembles them all together as : delimited. There is only one user of FILESEXTRAPATHS in oe-core (qt4-tools-native, which uses : anyway) and none in oe. Change the split() in utils.bbclass to split on : instead of whitespace. When splitting on a defined string (":") we must be careful to handle the empty string case which returns [''] instead of []. Tested building qt4-tools-native and core-image-minimal for surgarbay from meta-intel with a couple extra layers with FILESEXTRAPATHS modifications added. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Phil Blundell <pb@pbcl.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: rename u-boot_git.bb to u-boot_${PV}.bbDarren Hart2011-05-271-0/+0
| | | | | | | | | | | | | | | | | | | | | | | In order to facilitate reuse of the oe-core u-boot recipe, there needs to be some assurance that the oe-core version won't change without a clear indicator to people extending it. By renaming the recipe to include its version string instead of "git", BSP layers can extend a specific base version of u-boot, ie. u-boot_2011.03.bbappend. When 2011.06 becomes available, we can create that file without instantly breaking all the BSPs depending on oe-core version of the recipe. As a matter of policy I would recommend we not carry more than 2 versioned u-boot recipess at any given time. This will provide BSP layers time to migrate to the newer version, without cluttering oe-core with numerous stale versions of u-boot. We may decide later to resurrect u-boot_git.bb as an AUTOREV recipe to faciliate upstream development on u-boot in the oe environment. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Koen Kooi <koen@dominion.thruhere.net> Cc: Jason Kridner <jkridner@beagleboard.org>
* u-boot: remove UBOOT_MACHINE and COMPATIBLE_MACHINESDarren Hart2011-05-272-6/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | oe-core does not define any machines, so it does not make sense to add machine specific information in the oe-core u-boot recipe and infrastructure. Also note that COMPATIBLE_MACHINES is not easily extended due to its regex syntax: "(machine_a|machine_b)", making it difficult to extend the u-boot recipe in bbappend files without resorting to machine specific overrides. Remove COMPATIBLE_MACHINES and the default UBOOT_MACHINE from the recipe and insert some anonymous python into u-boot.inc to raise SkipPackage if UBOOT_MACHINE is not set (this ensures 'world' still works for machines that can't build u-boot). UBOOT_MACHINE must now be specified in each machine config that requires u-boot. This is an improvement over requiring machine specific overrides in every BSP layer's u-boot_git.bbappend file. For example, a beagleboard machine config currently contains: UBOOT_ENTRYPOINT = "0x80008000" UBOOT_LOADADDRESS = "0x80008000" With this change, it must now contain: UBOOT_MACHINE = "omap3_beagle_config" UBOOT_ENTRYPOINT = "0x80008000" UBOOT_LOADADDRESS = "0x80008000" So long as the SRC_URI in the base recipe can build a working u-boot for a given machine, there is no need to create a u-boot_git.bbappend file. If additional patches are deemed necessary, a BSP layer creates a u-boot_git.bbappend file and extends the SRC_URI to include general or machine specific backports. Note: I used bb.note() instead of bb.debug() to ensure the message at least makes it to the console. From what I could gather, bb.debug() doesn't go anywhere during recipe parsing. Signed-off-by: Darren Hart <dvhart@linux.intel.com> Cc: Richard Purdie <richard.purdie@linuxfoundation.org> Cc: Koen Kooi <koen@dominion.thruhere.net> Cc: Jason Kridner <jkridner@beagleboard.org> Cc: Chris Larson <clarson@kergoth.com>