summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* transfig-native: remove, nothing depends on itRoss Burton2013-09-172-40/+0
| | | | | | | | (From OE-Core rev: 3ba57642ceca73c601e4297e1b2abd8a4ccd671b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: fix typo in PACKAGECONFIGChen Qi2013-09-171-1/+1
| | | | | | | | | | Fix typo, change PACAKGECONFIG to PACKAGECONFIG. (From OE-Core rev: 77363d06121ceec264e06165ddda7b829c963301) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: fix failures of LSB python-runtime testsHongxu Jia2013-09-171-1/+0
| | | | | | | | | | | | | | | | | It has been fixed in: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=e261c1760d8a660c13cd00039a4812d51f47f3df But there is a typo in: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=78ac027f2ac6c6663fff7080eabbd3d09c1241bb It missed to remove an extra "--with-wctype-functions" in EXTRA_OECONF [YOCTO #5154] (From OE-Core rev: 4672b10ff9b6fcbfc446cabc4323387be21053cb) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: Allow resizecons on x86_64Li Zhijian2013-09-172-1/+30
| | | | | | | | (From OE-Core rev: cec49d5083f749d9886207e88648ddd4c12fbc87) Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kbd: Fix coding sytleLi Zhijian2013-09-171-1/+2
| | | | | | | | (From OE-Core rev: 2ababaf74255e7ad43cc951f2f2bc569ef955837) Signed-off-by: Li Zhijian <lizhijian@cn.fujitsu.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* LSB 4.1 Library Check: fix unable to find library libqt-mt.so.3Hongxu Jia2013-09-171-0/+11
| | | | | | | | | | | | | | | The libqt-mt is tested by lsb-dist-checker and lsb-test-desktop, and it locates in meta-qt3 layer. So if meta-qt3 is not added, there should be a warning to call attention; if added, it will add libqt-mt to RDEPENDS. [YOCTO #5153] (From OE-Core rev: f646f96015b408f4c6d56998f08178a69ed9f2a6) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cdrtools-native: Update from 3.00 to 3.01a17Jason Wessel2013-09-172-30/+24
| | | | | | | | | | | | | | The update is needed to support generation of EFI boot images that work with optical media. Specifically the "-eltorito-platform efi" capability for mkisofs is needed. [YOCTO #4100] (From OE-Core rev: aaa85b0706197423786dfeae386dbb402ee15684) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bootimage.bbclass: Move fat image creation into a functionJason Wessel2013-09-171-52/+58
| | | | | | | | | | | | | | | In order to call the fat image creation multiple times it needs to be in its own function. A future commit will make use of the new function to additionally create EFI image files for use with an ISO. [YOCTO #4100] [YOCTO #1913] (From OE-Core rev: 6d5181dc68766f42416a41f4988e8400d37fd7fa) Signed-off-by: Jason Wessel <jason.wessel@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: set acpaths to avoid "Argument list too long" errorRobert Yang2013-09-172-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There would be an error when the TMPDIR is long/deep, for example when len(TMPDIR) = 350 while our supported longest value is 410: [snip] aclocal: error: cannot open xxx autoreconf: aclocal failed with exit status: 1 ERROR: autoreconf execution failed. [snip] Let aclocal use the relative path for the m4 file rather than the absolute would fix the problem. Another fix is that we can modify autotools.bbclass to let it use the relative path rather than the absolute, but I don't think that we have to do that based on the following 2 thoughts: * The coreutils is the only recipe which has this issue as far as we know when len(TMPDIR) <= 410, because it has the most amount of m4 files (more than 400 ones). * That would impact all the recipes which use autotools.bbclass, and we are not sure about the side effect, for example, it would break the build there is a sub-configure. [YOCTO #2766] (From OE-Core rev: 22ac874512c2c1213aae8e1644bd59050b37a63c) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vala: add bison-native depends for vala-nativeRandy MacLeod2013-09-171-1/+1
| | | | | | | | | | | | vala-native builds were working because most systems have bison installed on the host. Add an explicit dependency on bison-native since bison isn't a sanity checked host tool. (From OE-Core rev: 4bcc087290661544dd5f6466d2d6ab74488f34ec) Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* udev: avoid autosuspend of USB input devicesNitin A Kamble2013-09-172-0/+26
| | | | | | | | | | | | | | | | | | | | | | Some of the external USB devices has internal USB hub, which make them look like "fixed" rather than "removable". And USB autosuspend does not work with some of these devices resulting in inoperable pointing device. Now the code detect these false "fixed" devices by looking at their parents. If any of their parent is "removable", then USB autosuspend is not enabled for that device, which keeps the pointing device functional. Fixes bug: [YOCTO #5166] (From OE-Core rev: d74a0ecdbc85a482cab6e7eae8dcb48185d44d84) Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: Fix comment typo spotted by Mark HatleRichard Purdie2013-09-171-1/+1
| | | | | | (From OE-Core rev: 27e7162840482c7790480be5f52c7651d5b71794) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkit-gtk: remove compile-three-times hackRoss Burton2013-09-171-20/+0
| | | | | | | | | | Remove the hack to handle Make 3.82 which ran make three times, as we sanity check Make and refuse to build with the broken release. (From OE-Core rev: dccd55eaeaee123238372c02c34d476d68816232) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: Try to figure out NFS root interface if using DHCPJukka Rissanen2013-09-171-8/+15
| | | | | | | | | | | | The commit c73487302270a7c2d3bbbb191ce1dd63ee2016dc missed the case where the NFS is using DHCP. [YOCTO #5176] (From OE-Core rev: 29be8e79a200d33555d2887578975e33b8417795) Signed-off-by: Jukka Rissanen <jukka.rissanen@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: remove patch for CVE-2012-2871Ross Burton2013-09-172-37/+1
| | | | | | | | | | | This CVE patch is actually against Chromium as they ship an internal fork of libxml2 and breaks ABI. The real issue has been resolved in libxslt 1.1.27, and we're shipping 1.1.28. (From OE-Core rev: e6c60252ab4ba6842f63c6b8a519a85f2ff238fb) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* utils: Update bb.which reference and other syntax cleanupRichard Purdie2013-09-171-5/+3
| | | | | | | | | | | * bb.which -> bb.utiis.which() * Use modern form of datastore access * Use True, not 1 * Drop pointless imports (From OE-Core rev: 106a4f5b41e5bdeabe588b9ba362f3693b1a9989) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autotools: Remove .la files if rebuilding non out of tree softwareRichard Purdie2013-09-171-4/+10
| | | | | | (From OE-Core rev: bcf83bb604906361db98003127b90c422e822322) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: genericx86 meta data factoringBruce Ashfield2013-09-143-3/+3
| | | | | | | | | | | | | | | | | | | | | | Updating the 3.10 meta branch to import the following commits from Darren Hart: 285f93b meta/common-pc-64: Add USB 3.0 support 75072e4 meta/common-pc*: Refactor common-pc-64 to reuse common-pc drivers da06bde meta/common-pc: Split out CPU and Drivers config fragments 5f55e40 meta/common-pc: Cleanup common-pc.cfg and common-pc-gfx.cfg 0a3f784 meta/common-pc: Add common Wifi drivers f4b9f5e meta/common-pc: Add common Realtek and Atheros Ethernet drivers 4d9d3eb meta/common-pc: Build Ethernet and Wifi drivers as modules 13141ee meta/common-pc: Refactor Ethernet and Wifi options These are in support of a new genericx86 multi-target BSP. (From OE-Core rev: 1ab0813c819d3b785178faa458486efa6992c636) 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>
* lttng: Enable ptest support.Stefan Seefeld2013-09-143-2/+62
| | | | | | | | (From OE-Core rev: d0d184045e8034ddbc77549e681f187e12ab1d08) Signed-off-by: Stefan Seefeld <stefan_seefeld@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: add ptestRoy.Li2013-09-142-1/+17
| | | | | | | | (From OE-Core rev: dc3ac3d406bd6152eaa195e90b95bcdb0ac31121) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: remove unused filesChen Qi2013-09-143-14/+0
| | | | | | | | | | | | | | | | The 'need' and 'provide' files are there for simpleinit compatability, according to the comments in these two files. However, we don't use simpleinit and there's even no simpleinit recipe in OE. Besides, these two files are not installed. This patch removes these two unused files. (From OE-Core rev: 05ac5627208c98007cd4c7aed9d76f179cd974a9) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysvinit: fix indentationChen Qi2013-09-141-4/+4
| | | | | | | | | | Fix indentation in SRC_URI to conform to the indentation convention in OE. (From OE-Core rev: e05e7016fac7c665a23865dce18b816e01dbd51e) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* boot-directdisk: Allow for EFI-only boot direct disk imagesJoão Henrique Ferreira de Freitas2013-09-142-10/+60
| | | | | | | | | | | | | Condition building PCBIOS legacy images on MACHINE_FEATURES containing "pcbios" or not containing "efi". This ensures existing BSPs will continue to get the old PCBIOS legacy-only images. New BSPs can add "efi", "pcbios", or both. The images created likewise support one or the other or both. (From OE-Core rev: c58aceee7dc243467dd87f07ccc61859f8d945e6) Signed-off-by: João Henrique Ferreira de Freitas <joaohf@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils-native: Fix build on distros with gcc 4.8Khem Raj2013-09-142-2/+45
| | | | | | | | | | | | | The patch redhat-portability.diff causes this issue so lets revert the portion which was using %a instead of %m thats recommended anyway, redhat patch seems to be targetting old compilers. (From OE-Core rev: c1cbc57eb80d2cab9a80d5e5aa65419f40eefb15) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* eglibc_2.18.bb: Fix IFUNC support for ARM REL relocationsKhem Raj2013-09-142-0/+44
| | | | | | | | | | | | | This should fix the case where neon code is emitted for machines which dont have neon unit in the chip [YOCTO# 5161] (From OE-Core rev: 516e6f065a1bed0d95ffd1c8a4d8e135d834af94) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-vmware: disable VMWGFXRoss Burton2013-09-142-2/+77
| | | | | | | | | | | | | Our Mesa doesn't yet ship the XA Gallium state tracker that the VMWGFX sub-driver needs, so just disable vmwgfx. Also remove a spurious xvmc dependency. (From OE-Core rev: a6f84a0317997c3f49e136381f8d2f2f5cadd292) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: link runlevel from systemctlRoy.Li2013-09-141-1/+5
| | | | | | | | | | using update-alternatives to link runlevel from systemctl, as on Fedora 18 (From OE-Core rev: 8909b3b71b2ac792ae092b8f0a6c2ade28f6b73b) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* apmd: Add systemd supportMuhammad Shakeel2013-09-142-2/+18
| | | | | | | | | | -Remove dependency on meta-systemd (From OE-Core rev: 9e963fe587dda3ce77707194fc5dd029188c76d8) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oprofileui-server: Add systemd supportMuhammad Shakeel2013-09-142-2/+17
| | | | | | | | | | -Remove dependency on meta-systemd (From OE-Core rev: 177bf318bcd3dd2bfb3bec094b1f5ccac7bdd9ac) Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* LSB Command Check: fix install_initd and remove_initd not foundHongxu Jia2013-09-141-2/+2
| | | | | | | | | | | | | | | | | The install_initd and remove_initd are linked to /sbin/chkconfig for lsb core test, but chkconfig has been moved from /sbin to /usr/sbin in order to fix QA warning about unsafe references in binaries. (In commit e486242db83297701803866bea971a2f1a1135fe) Let install_initd and remove_initd link to /usr/sbin/chkconfig could fix this issue. [YOCTO #5152] (From OE-Core rev: 789c4c13c5095a2865d1ee1b242141b5b076bed5) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* anjuta-remote-run: removeRoss Burton2013-09-142-24/+0
| | | | | | | | | This is from the Anjuta integration which was removed many years ago. (From OE-Core rev: db488bf8130dba2ad8771b0634e3c5de452f23f2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* adt-installer: fix opkg repo nameLaurentiu Palcu2013-09-142-2/+2
| | | | | | | | | | | | | I mistakenly named the allarch opkg repo the same as nativesdk one... This patch fixes it. [YOCTO #5181] (From OE-Core rev: 98f39b0ae4ed45194a165de3913f27745481cb7a) Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-libc-headers: Add big warning about antisocial behaviourRichard Purdie2013-09-141-0/+27
| | | | | | | | | | I'm getting concerned with the number of people forking this recipe and not understanding what they're doing. I'm therefore proposing adding in a suitable warning to people thinking of copying it. (From OE-Core rev: c27ac156bcaf3193d52f456480947b0cfaef3c72) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib/oeqa/runtime: timeout increasesStefan Stanacar2013-09-142-2/+2
| | | | | | | | | | | Increase the timeout for smart commands as under load for qemumips it's still to small. Also give ping more time fixing a potential timeout for sato systemd. (From OE-Core rev: daa3ad5807f6fc0d15b9310937d07a16edac6d22) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf/package: Collapse PKGDATA_DIR into a single machine specific ↵Richard Purdie2013-09-1413-79/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | directory Currently we have a hierarchy of pkgdata directories and the code has to put together a search path and look through each in turn until it finds the data it needs. This has lead to a number of hardcoded paths and file globing which is unpredictable and undesirable. Worse, certain tricks that should be easy like a GL specific package architecture become problematic with the curretn search paths. With the modern sstate code, we can do better and construct a single pkgdata directory for each machine in just the same way as we do for the sysroot. This is already tried and well tested. With such a single directory, all the code that iterated through multiple pkgdata directories and simply be removed and give a significant simplification of the code. Even existing build directories adapt to the change well since the package contents doesn't change, just the location they're installed to and the stamp for them. The only complication is the we need a different shlibs directory for each multilib. These are only used by package.bbclass and the simple fix is to add MLPREFIX to the shlib directory name. This means the multilib packages will repackage and the sstate checksum will change but an existing build directory will adapt to the changes safely. It is close to release however I believe the benefits this patch give us are worth consideration for inclusion and give us more options for dealing with problems like the GL one. It also sets the ground work well for shlibs improvements in 1.6. (From OE-Core rev: 1b8e4abd2d9c0901d38d89d0f944fe1ffd019379) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Version bump for DEPLOY_DIR layout changeRichard Purdie2013-09-141-1/+1
| | | | | | | | | Increase the version to signify the layout change of the images in the deploy directory. (From OE-Core rev: 4246e7dd59800a1d6c6d02c00f4e86eeac020767) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: include machine name in DEPLOY_DIR_IMAGEPaul Eggleton2013-09-143-2/+9
| | | | | | | | | | | | | | | | | | | This allows a clean seperation between image outputs from different machines, and makes it possible to have convenience symlinks to make the output ready to deploy. This did require some surgery in runqemu; if explicit paths to the image and kernel are not supplied then DEPLOY_DIR_IMAGE needs to be determined from bitbake or set in the environment. However the script does try to avoid requiring it unless it really is needed. Corresponding changes were made in the automated testing code as well. Based on an RFC patch by Koen Kooi <koen@dominion.thruhere.net> (From OE-Core rev: 7e90261aec61f79680b5eaeaf5b18c7b795412a4) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* icu-native: do_install: Segmentation faultRobert Yang2013-09-142-1/+32
| | | | | | | | | | | | | | | There was a "Segmentation fault" error when build icu-native when the TMPDIR is in a deep directory (for example, when len(readlink -f $TMPDIR == 410)), use LARGE_BUFFER_MAX_SIZE for cmd rather than SMALL_BUFFER_MAX_SIZE would fix the problem, this should be a misplay because other cmd uses LARGE_BUFFER_MAX_SIZE. [YOCTO #5171] (From OE-Core rev: ebfdddc23ff78231a819c62c8ffcced9633aa08b) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perf: source should be ready after do_unpackRobert Yang2013-09-141-0/+3
| | | | | | | | | | | | | | | | | | | In perf.bb: S = "${STAGING_KERNEL_DIR}" So the source should be ready after the do_unpack, and we need this: do_unpack[depends] += "virtual/kernel:do_populate_sysroot" Otherwise, maybe no source after do_unpack. [YOCTO #5168] (From OE-Core rev: 01d3b15518b981199120b3b9c6923678244aefdc) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake.conf: Stop providing ${P} and ${PF} by defaultRichard Purdie2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For a long time we've provided PN-PV and PN-PV-PR by tweaking PROVIDES. This looks nice at first glance however it turns out to be a bit problematic. Taking make as an example where there are two versions, 3.81 and 3.82, what should "bitbake make-3.81" do? Currently it builds make-3.81 and make-3.82 and breaks in interesting ways. Is that a bitbake bug? Well, it certainly shouldn't try and run the build. Why is it building 3.82 though? Its due to finding a dependency on "make-dev" and then trying to figure out what provides it? The answer is "make" and the default version of "make" is 3.82. So arguably, finding "make-3.81" should infer PREFERRED_VERSION_make = "3.81". Doing so resolved the above problem since now "make" resolves to "make-3.81". So what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make-3.82" That is clearly an error, easy. So finally what about if we have Recipe A: DEPENDS = "make-3.81" and Recipe B: DEPENDS = "make" The first recipe infers the PREFERRED_VERSION_make = "3.81" and then forces that version on everything else. Is that desired? Probably not in most cases, at least not silently. As mitigation, we could print a WARNING about this happening. The final part of the problem is that we can ony figure this out within bitbake itself. That means we'd have to teach bitbake about the PN-PV format of PROVIDES which is breaking the separation between bitbake and the metadata. We can't win :(. Nobody that I know of is using or relying on this functionality so perhaps we should just remove it instead which is what this patch does. Opinions? (From OE-Core rev: a87c205bb6cefd5e1a41b8e7ef02b5bfa380e3b6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate.bbclass: fix parallel building issueRoy.Li2013-09-141-1/+1
| | | | | | | | | | | | | | | | | | | | | | sstate_package creates hardlink from sysroot to SSTATE_BUILDDIR, then sstate_create_package will store SSTATE_BUILDDIR into a archive file by tar, but once other packages install the same file into sysroot, the creating the archive file will fail with below error: DEBUG: Executing shell function sstate_create_package tar: x86_64-linux/usr/share/aclocal/xorg-macros.m4: file changed as we read it This kind of error is harmless, use --ignore-failed-read to ignore it. The error in tar occurs when the timestamp of the file changes and this can happen when the number of symlinks change. The file will be included in the archive. [YOCTO #5122] (From OE-Core rev: 4b3e353a532c7b68b0bb86df4a2fcc44f8bb3ef2) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libnewt-python: Don't write a whiptail packageRichard Purdie2013-09-121-0/+1
| | | | | | | | | The whiptail package is written by the libnewt recipe so for the python version we need to ensure its not in PACKAGES. (From OE-Core rev: b26157a8b575aa7b5c96ffe782fc23ec0920311c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_rpm: Only remove trailing whitespace, not all whitespaceRichard Purdie2013-09-121-2/+2
| | | | | | (From OE-Core rev: 06cb4deba6e4df4ffe3015602d5997b26d28778b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* weston: as weston-launch depends on PAM, control it with a PACKAGECONFIGRoss Burton2013-09-111-2/+4
| | | | | | | (From OE-Core rev: fb430271da67d7ec98c285a3420b00db737cae55) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* clutter: fix compilation when building without X11 backendRoss Burton2013-09-112-1/+59
| | | | | | | | | | | | | If Clutter is building the Wayland backend but not the X11 backend, the Cogl support doesn't get enabled so the Wayland backend (which uses it) fails to compile. Backport a fix from upstream to fix this situation. (From OE-Core rev: 6df36a004210901acceff4a201d0f910d99eccfe) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x11vnc: add dependencies for xrandr/xfixes/xdamage/xtstRoss Burton2013-09-111-1/+1
| | | | | | | | | | | Inspired by a patch by Martin Jansa but with these libraries required, as a VNC server without them is suboptimal. Don't add an option for Xinerama as our X server always disables it. (From OE-Core rev: 4bca0b8adcac6eebc4466a2eea03de3493bf1cc4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_rpm: Ensure empty strings aren't passed to attemponly rpm codeRichard Purdie2013-09-111-2/+2
| | | | | | | | | If empty strings are passed to the rpm attemptonly code, it breaks. This ensures we don't do that. (From OE-Core rev: 6a0d5a3158608364f6baa11fe9ab7fa1f8e251ab) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-vmware: respect opengl DISTRO_FEATURERoss Burton2013-09-111-2/+2
| | | | | | | | | | | | | | Conditionalise the GL dependencies on the opengl DISTRO_FEATURE so this driver can build without the opengl feature active, as the configure script will enable/disable the GL sub-driver depending on the presence of these libraries. This is an interim patch to fix the autobuilder, a more complete patch heading upstream to make the GL sub-driver deterministic will follow. (From OE-Core rev: 66b7c59442cc494179418995292c57bab56fada3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bluez4/5: Add EXCLUDE_FROM_WORLD = 1Saul Wold2013-09-112-0/+3
| | | | | | | | | | | | | | | We can't build both recipes in the world build as there is a collision of package name and PR values. Specificly the libasound-module-bluez which is the same in both goes backwards from r5 (bluez4) -> r0 (bluez5) and the subpackage_metadata check fails: ERROR: Recipe lib32-bluez5 is trying to change PR from 'r0' to 'r5'. This will cause do_package_write_* failures since the incorrect data will be used and they will be unable to find the right workdir. [YOCTO #5165] (From OE-Core rev: 3653500c7e5d365ddc2868d985c6001d40123672) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* xf86-video-intel: disable DRI2 tests if no DRI2 is availableRoss Burton2013-09-112-0/+52
| | | | | | | | | | Somehow this slipped past the initial testing and can cause build errors in non-GL distros. (From OE-Core rev: 975412f446066215a94be78a7f7e1db9e28ebbbf) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
OpenPOWER on IntegriCloud