summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* libpam / xtests: remove bash dependencyWenzong Fan2014-09-292-1/+228
| | | | | | | | | | | | | | | | | There's not bash specific syntax in the xtests scripts: $ cd Linux-PAM-1.1.6/xtests # replace /bin/bash to /bin/sh and check the bashisms: $ checkbashisms *.sh No output So the runtime dependency to bash could be removed. (From OE-Core rev: 1917bf7aa74aa1b86756c73c56537db2591115e5) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gst-plugins-base: fix build failure for x86Jackie Huang2014-09-292-1/+40
| | | | | | | | | | | On x86, EMMINTRIN is defined but not usable without SSE so check for __SSE__ and __SSE2__ as well. (From OE-Core rev: 556a19423d15c7c13f60d57528a3b880f95750b9) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: selinux/flask.h should respect to with_selinuxRobert Yang2014-09-292-0/+40
| | | | | | | | | | | | | | Fixed when build with meta-selinux even with --without-selinux: runcon.c:49:28: fatal error: selinux/flask.h: No such file or directory # include <selinux/flask.h> ^ compilation terminated. (From OE-Core rev: d52a606c8a75496f3b7239adc19fdb66e3ae576a) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemd: disable resolv.conf symlink unless resolved is enabledPeter A. Bigot2014-09-292-0/+36
| | | | | | | | | | | | | | | | | | | | The tmpfiles configuration in systemd unconditionally creates a symlink from /etc/resolv.conf to the location where systemd's resolved service will place the real file. This link is only appropriate when resolved is enabled and running: its presence prevents connman or other systems from providing a working resolv.conf when systemd is not assigned that responsibility. OE has not yet enabled systemd's networkd or resolved by default. There is a TODO in the systemd source to fix this, but it has not been addressed upstream. This patch comments out the corresponding line when resolved is not enabled in the package configuration. (From OE-Core rev: 7e2b05a6f59209687829225878a19a1dad8143b9) Signed-off-by: Peter A. Bigot <pab@pabigot.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Change overlapping files warning to a fatal errorRichard Purdie2014-09-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | When files overlap in the sysroot, something bad usually happened. We've had two independent cases recently where a couple of months after one of these warnings was shown, builds failed due to corruption. This change moves the warning to become a fatal error. The complaint I've had about this is that we need to tell the user what happened and more importantly how to recover from it. If we could recover from it, great but the trouble is we simply don't know what happened. As a compromise, we can document several of the possible scenarios in the error message. We don't normally go to this level of detail however in this case, I'm lacking other viable alternatives. I do believe it is important to stop as corruption occurs rather than letting the build contunue into territory that is not deterministic amongst other things. The complex message is followed by a simpler one in case the long message is too much for the user. (From OE-Core rev: 179ac7de03977b6e440409eddb2166819e07286a) (From OE-Core rev: 4b503f25f1ef8f554d3c76d88399db379dc818cc) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: Update to dizzy head revisionRichard Purdie2014-09-231-1/+1
| | | | | | (From OE-Core rev: e6c6d3fcfd2faf867e8145d25c1ba197fb9ee6b5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sanity.conf: Update minimum bitbake version to 1.23.2 due to event changesRichard Purdie2014-09-231-1/+1
| | | | | | (From OE-Core rev: b4e2a769e8def2e78ffca3f006a0cc88407aaeda) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Mark opkg-utils as ABISAFE for update-alternatives usageRichard Purdie2014-09-231-0/+2
| | | | | | | | | | | Currently linux-firmware rebuilds for each machine due to its usage of update-alternatives which in turn means a dependency on opkg-utils. Marking opkg-utils as ABISAFE is the only option we have right now to avoid this. (From OE-Core rev: 6829c0e161c4a8cde6624f211865922fce62d4fa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* update-rc.d/systemd: Remove OVERRIDES dependencyRichard Purdie2014-09-232-0/+3
| | | | | | | | | | | | | Taking run-postinsts and building for two machines which have different OVERRIDES leads to two different sets of stamps for an allarch package. We don't need to depend on OVERRIDES in these classes, the end resulting variables are good enough. We can therefore exclude the dependency and allow a single package to be generated for run-postinsts. (From OE-Core rev: fdc949154e64afb41dd4db3a97be74a15963128d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* layer.conf: Add in useradd dependencies as ABISAFE dependenciesRichard Purdie2014-09-231-0/+3
| | | | | | | | | | Currently allarch recipes using useradd rebuild each time MACHINE changes which is not desireable. Adding the useradd dependencies to this list ensures they do not change under these circumstances. (From OE-Core rev: 7743a309017f0fb9286f00b1f6f546ee95c05303) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man: fix not support xz/bz2 compressionHongxu Jia2014-09-231-1/+2
| | | | | | | | | | | | In oe-core, bunzip and unzx located in /usr/bin/ rather than /usr, so tweak man's config. [YOCTO #6750] (From OE-Core rev: a8f07626d627b49913835778cc8039accd8b9896) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: make setregid02 be able to passRoy.Li2014-09-232-0/+62
| | | | | | | | | | | | [YOCTO #6748] replace "nobody" group with "nogroup", since the user "nobody" belongs to "nogroup" group and no "nobody" group in oe-core (From OE-Core rev: 3fc1b5acb50aa864d386f69a1c0d0db0425f970c) Signed-off-by: Roy.Li <rongqing.li@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* systemtap: disable libvirtWenzong Fan2014-09-233-0/+43
| | | | | | | | | | | | | | | | | libvirt is automatically linked to if present, this undetermined dependency may cause build errors like: ../lib/libvirt.so: undefined reference to `libssh2_channel_open_ex' ../lib/libvirt.so: undefined reference to `libssh2_session_hostkey' ... Both libvirt and libssh2 are not oe-core recipes for now, just disable libvirt to fix this issue. (From OE-Core rev: 815b44914eb30b86dfce0e81ffda7884e0efcc34) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* documentation.conf: document IMAGE_BOOT_FILESMaciej Borzecki2014-09-231-0/+1
| | | | | | | | | | Document IMAGE_BOOT_FILES variable. (From OE-Core rev: 8007f41aa824db2ee681d9dd98a0b06f44fc9d6d) Signed-off-by: Maciej Borzecki <maciej.borzecki@open-rnd.pl> Signed-off-by: Maciek Borzecki <maciek.borzecki@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* uninative: Add uninative - a way of reusing native/cross over multiple distrosRichard Purdie2014-09-232-0/+92
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These patches are the start of a new idea, a way of allowing a single set of cross/native sstate to work over mutliple distros, even old ones. The assumption is that our own C library is basically up to date. We build and share a small tarball (~2MB) of a prebuilt copy of this along with a patchelf binary (which sadly is C++ based so libstdc++ is in there). This tarball can be generated from our usual SDK generation process through the supplied recipe, uninative-tarball. At the start of the build, if its not been extracted into the sysroot, this tarball is extracted there and configured for the specified path. When we install binaries from a "uninative" sstate feed, we change the dynamic loader to point at this dynamic loader and C librbary. This works exactly the same way as our relocatable SDK does. The only real difference is a switch to use patchelf, so even if the interpreter section is too small, it can still adjust the binary. Right now this implements a working proof of concept. If you build the tarball and place it at the head of the tree (in COREBASE), you can run a build from sstate and successfully build packages and construct images. There is some improvement needed, its hardcoded for x86_64 right now, its trivial to add 32 bit support too. The tarball isn't fetched right now, there is just a harcoded path assumption and there is no error handling. I haven't figured out the best delivery mechanism for that yet. BuildStarted is probably not the right event to hook on either. I've merged this to illustrate how with a small change, we might make the native/cross sstate much more reusable and hence improve the accessibility of lower overhead builds. With this change, its possible the Yocto Project may be able to support a configured sstate mirror out the box. This also has positive implications for our developer workflow/SDK improvements. (From OE-Core rev: e66c96ae9c7ba21ebd04a4807390f0031238a85a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* irda-utils: remove inherit autotoolsRoss Burton2014-09-231-1/+1
| | | | | | | | | irda-utils doesn't use autotools, so don't inherit it. (From OE-Core rev: d5e2a59ab59e3d67d09c5f25b8623186af855e17) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: update to v3.14.19Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | Updating to the latest korg -stable update. (From OE-Core rev: 7212dcb3a67b9a9b844b74e997d2e3ea7902555f) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.55Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | Updating to the latest korg -stable update. (From OE-Core rev: 9745ffc0ae25be980d92f195937cef6d1f406ab2) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: bump to v3.17-rc6Bruce Ashfield2014-09-232-12/+12
| | | | | | | | | | Updating the 3.17 recipe to -rc6. This is nearly the release kernel, and should have very few changes aftert this point. (From OE-Core rev: 845e01d906982c2147828b97129e95e8a79dce7c) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: switch to dedicated 3.17 repositoryBruce Ashfield2014-09-231-1/+1
| | | | | | | | | | The 3.17 repository is ready, so we no longer need to reuse the linux-yocto-dev tree. (From OE-Core rev: c304674833360e0e2dceca3ebeb535025597e46f) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.17: update to v3.17-rc5Bruce Ashfield2014-09-232-12/+12
| | | | | | | | | Bumping the SRCREVs to import the latest korg -rc. (From OE-Core rev: 8ae153f7da3244c3dd24cc5dbd722af26624201b) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.14: update to v3.14.18 and -rt9Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | Refreshing the 3.14 kernel to a new korg stable and -rt release. (From OE-Core rev: 91204afeb508ae21f8f2a32c340ec85efbf33fd0) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* linux-yocto/3.10: update to v3.10.54 and -rt55Bruce Ashfield2014-09-233-16/+16
| | | | | | | | | The 3.10 kernel needed a refresh to the latest -stable and -rt releases. (From OE-Core rev: c7360e9e72f06dab2617e16ae546f4d8e5262fa1) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* oeqa/selftest: Added decorators to buildoptions.pyLucian Musat2014-09-221-0/+9
| | | | | | | (From OE-Core rev: ea393e90055ea13b0c5a6950dbd388e826a66623) Signed-off-by: Lucian Musat <georgex.l.musat@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel.bbclass: use one package split for all firmware filename extensionsCarlos Rafael Giani2014-09-221-4/+1
| | | | | | | (From OE-Core rev: dd5313228879487ca2b11fc5d38fb821a2a810a5) Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* u-boot: cleanup indentation and consolidate .inc fileDenys Dmytriyenko2014-09-225-36/+30
| | | | | | | (From OE-Core rev: 71525643909ac765e6b6a4b419cddae7d5812a8d) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* populate_sdk_base/meta-environment: Remove overlap from the twoRichard Purdie2014-09-222-33/+29
| | | | | | | | | | | | | | | | | | | | Currently we have the horrible situation where meta-environment packages the toolchain environment files and they get included in the SDK but are broken, then, the SDK code overwrites them with good versions. This is suboptimal. This change fixes the code in meta-environment to create working files and adds in the multilib support from populate_sdk_base, then we remove the code in that base bbclass and rely on the packages being installed if/as/when needed. This removes the duplication and the broken versions of the files, hopefully making all well. [YOCTO #6608] [YOCTO #6613] (From OE-Core rev: 063355e5965439c7b3253d692d7ab0ed1189d123) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta-environment: Fix TARGET_OS problem for ppcRichard Purdie2014-09-221-1/+2
| | | | | | | | | | | | | | | | Due to the use of the cross-canadian inherit, TARGET_OS can be reset to values other than the correct one, leading to generation of the wrong files. By expanding REAL_MULTIMACH_TARGET_SYS before the inherit, the correct OS value is preserved and we generate the right environment files. [YOCTO #6608] [YOCTO #6613] (From OE-Core rev: ae265973c96ff4b8b5580436647fc361490e134c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-plugins-bad: disable libssh2Wenzong Fan2014-09-222-0/+68
| | | | | | | | | | | | | | libssh2 is automatically linked to if present, this undetermined dependency may cause build errors like: .../x86_64-poky-linux/4.9.0/ld: cannot find -lssh2 libssh2 isn't an oe-core recipe, disable it for now. (From OE-Core rev: 0cc59247ece1ea134d060d3ff064b5561972a92b) Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* perl: remove unneeded patches in ptest directoryChong Lu2014-09-221-1/+1
| | | | | | | | | | | The perl patches have been copied to ptest directory and these patches in target rootfs are linked to build dir. The ptest of perl doesn't need these patches, so remove them from target. (From OE-Core rev: 1982095255917befd93ed14f9abc1f9fc4149f99) Signed-off-by: Chong Lu <Chong.Lu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: obey LDFLAGSChristopher Larson2014-09-221-1/+1
| | | | | | | (From OE-Core rev: 7191b6b7503a5a17f93bd61283f22d409c5cb17b) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* irda-utils: obey LDFLAGSChristopher Larson2014-09-222-5/+88
| | | | | | | | | | While we're at it, also switch to explicit variable passing rather than relying on make -e, and pass V=1 so the actual commands hit the logs. (From OE-Core rev: 7106f840b7d2a71171131c3c3e5fc311718ca718) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* blktrace: obey LDFLAGS for btrecordChristopher Larson2014-09-221-2/+6
| | | | | | | (From OE-Core rev: 43be08bbfc3fd7ae2a8143ccd5d51d48394f4e77) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* hostap-utils: obey LDFLAGSChristopher Larson2014-09-222-0/+28
| | | | | | | (From OE-Core rev: 6b2395210e8c7fd7eb91fa78e043a811c3c0af3d) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* setserial: obey LDFLAGSChristopher Larson2014-09-222-0/+25
| | | | | | | (From OE-Core rev: aaebe0f814a031b06ba72bc9de8b5ec4dbf80f0a) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ossp-uuid: obey LDFLAGSChristopher Larson2014-09-222-0/+27
| | | | | | | (From OE-Core rev: 3a006550fcc99af58fa5d933160f169e97c3a6de) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdbm-1.8.3: obey LDFLAGSChristopher Larson2014-09-222-1/+24
| | | | | | | (From OE-Core rev: efdc4bff8dff4bf065a7c65e7d1c9f5460839a24) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* zlib: obey LDFLAGS for testsChristopher Larson2014-09-222-0/+46
| | | | | | | (From OE-Core rev: c91d9153d5dc6750d1f4c7b3be58da0a1248245b) Signed-off-by: Christopher Larson <kergoth@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: Added zip-native as a DEPENDSAlejandro Hernandez2014-09-221-1/+1
| | | | | | | | | | | The Makefile checks for zip during installation [YOCTO #6699] (From OE-Core rev: a6e8ced3fa8e8e2aa3df0798b80eb26e5ebc4b15) Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* flex: fix the deps for ptest buildsChristopher Larson2014-09-221-1/+1
| | | | | | | | | | | Building the tests for flex requires flex-native and bison-native, but the attempt to add this dependency was done incorrectly. Use an inline python conditional based on PTEST_ENABLED instead. (From OE-Core rev: fce2be6dcf8e7320b7b9df9947745e78fd160815) Signed-off-by: Christopher Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake.bbclass : Add support for cmake projects that use .S files.Philip Balister2014-09-221-0/+3
| | | | | | | | | | | | UHD and GNU radio use the cmake build system. The toolchain file made from cmake.bbclass does not set the variable needs by cmake projects that use .S files. UHD added some .S files and these changes are required to build recent UHD. (From OE-Core rev: 43ce4b804d433662fe77c6f5298060ba74a0e639) Signed-off-by: Philip Balister <philip@balister.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: fix overrides behaviour to remove SIGGEN_LOCKEDSIGS_i586Hongxu Jia2014-09-171-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Require a sig file which SIGGEN_LOCKEDSIGS_i586 is not null, but the actual SIGGEN_LOCKEDSIGS_i586 is null. Invoking 'bitbake -e' and we got: ... 3935 # $SIGGEN_LOCKEDSIGS_i586 [2 operations] 3936 # set /path/to/locked-sigs.inc:8576 3938 # del data_smart.py:406 [finalize] 3939 # "" ... It was caused by the following commit: ... (Bitbake rev: 899d45b90061eb3cf3e71029072eee42cd80930c) Author: Richard Purdie <richard.purdie@linuxfoundation.org> Date: Tue May 31 23:52:50 2011 +0100 bitbake/data_smart: Change overrides behaviour to remove expanded variables from the datastore ... We add prefix 't-' to type to workaround the overrides behaviour. (From OE-Core rev: f6a39cc957bf85ff43513f0b76afc3b2c9c906b6) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: set SIGGEN_LOCKEDSIGS_CHECK_LEVEL default to errorHongxu Jia2014-09-171-0/+2
| | | | | | | (From OE-Core rev: 65020364bd089afbb83cd216e7ae2f837077bfc5) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig.py: Replace '_'s with '-'s in SSTATE_LOCKEDSIGS* names.Randy Witt2014-09-171-0/+1
| | | | | | | | | | | | | | | | Using underscores in the "types" parts of the variable names can cause unexpected issues with overrides. For example, if you have both SSTATE_LOCKEDSIGS_x86_64 and SSTATE_LOCKEDSIGS_x86_64_i586, and i586 is in OVERRIDES, then you lose all of the contents in SSTATE_LOCKEDSIGS_x86_64 and thus don't get some of the locked sstate. Using '-'s in the variable names instead, eliminates these issues. (From OE-Core rev: 6662c412a949a9f6b602c848e6303b19db7e5272) (From OE-Core rev: 65f558a6f762fb13224091dc22903b58eeb9b392) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Improve the support for locked down sstate cache usageHongxu Jia2014-09-171-16/+27
| | | | | | | | | | | | | | | | | | | | | Add code in the sstate hash validation code to ensure it really did install these from sstate since if it didn't should to warn/abort the build. The judgment condition is: 1) If a build is replaced by locked sstate-cache, it will triger a warn/error; 2) If objects are not used from the locked cache, it will triger a warn/error; 3) Use SIGGEN_LOCKEDSIGS_CHECK_LEVEL variable controls whether this is just a warning or a fatal error or nothing to report. [YOCTO #6639] (From OE-Core rev: 305912dce61c4fed0cbf631aa98a9e6f29db88e4) (From OE-Core rev: 1683815695f39d4bad352348913f927ac8a1bcf5) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig: Improve to handle locking of multiple machinesRichard Purdie2014-09-171-13/+28
| | | | | | | | | | | | | | | | | Instead of a single monolithic SIGGEN_LOCKEDSIGS, split this into separate variables, one per sstate package architecture. Add in a new SIGGEN_LOCKEDSIGS_TYPES variable which lists the package architectures to load in. SIGGEN_LOCKEDSIGS_TYPES is made machine specific using overrides. Also sort the hashes in the lists by PN to make diffing them easier. (From OE-Core rev: d8b0ce35981931a39e7db9d8e78de6e009b34688) (From OE-Core rev: b42f305ce38b9e0f1a2b7cb9586bbabcd2d27429) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstatesig/sstate: Add support for locked down sstate cache usageRichard Purdie2014-09-172-0/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've been giving things some thought, specifically why sstate doesn't get used more and why we have people requesting external toolchains. I'm guessing the issue is that people don't like how often sstate can change and the lack of an easy way to lock it down. Locking it down is actually quite easy so patch implements some basics of how you can do this (for example to a specific toolchain). With an addition like this to local.conf (or wherever): SIGGEN_LOCKEDSIGS = "\ gcc-cross:do_populate_sysroot:a8d91b35b98e1494957a2ddaf4598956 \ eglibc:do_populate_sysroot:13e8c68553dc61f9d67564f13b9b2d67 \ eglibc:do_packagedata:bfca0db1782c719d373f8636282596ee \ gcc-cross:do_packagedata:4b601ff4f67601395ee49c46701122f6 \ " the code at the end of the email will force the hashes to those values for the recipes mentioned. The system would then find and use those specific objects from the sstate cache instead of trying to build anything. Obviously this is a little simplistic, you might need to put an override against this to only apply those revisions for a specific architecture for example. You'd also probably want to put code in the sstate hash validation code to ensure it really did install these from sstate since if it didn't you'd want to abort the build. This patch also implements support to add to bitbake -S which dumps the locked sstate checksums for each task into a ready prepared include file locked-sigs.inc (currently placed into cwd). There is a function, bb.parse.siggen.dump_lockedsigs() which can be called to trigger the same functionality from task space. A warning is added to sstate.bbclass through a call back into the siggen class to warn if objects are not used from the locked cache. The SIGGEN_ENFORCE_LOCKEDSIGS variable controls whether this is just a warning or a fatal error. A script is provided to generate sstate directory from a locked-sigs file. (From OE-Core rev: 7e14784f2493a19c6bfe3ec3f05a5cf9797a2f22) (From OE-Core rev: 884d4fa3e77cf32836f14a113c11489076f4a84d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-configure/gcc-common: Move preconfigure definition to common includeRichard Purdie2014-09-162-10/+10
| | | | | | | | | | | | | | | | | | | | | There is a race where: NOTE: recipe libgcc-initial-4.9.1-r0: task do_configure: Started NOTE: recipe gcc-runtime-4.9.1-r0: task do_preconfigure: Started | checking build system type... /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-deb/build/build/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/../config.sub: line 1711: syntax error near unexpected token `;;' | /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-deb/build/build/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/../config.sub: line 1711: ` ;;' | configure: error: /bin/bash /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-deb/build/build/tmp/work-shared/gcc-4.9.1-r0/gcc-4.9.1/libgcc/../config.sub x86_64-linux failed | WARNING: exit code 2 from a shell command. so we need to make sure the preconfigure task executes in all shared work contexts. (From OE-Core rev: 3c30331d6eaf804b83a6d27189a12efc94310e91) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcrypt: Fix ARM assembly when building __PIC__Jackie Huang2014-09-162-0/+171
| | | | | | | | | | | libgcrypt.so.20 contains .text relocations, backport a patch to fix it. (From OE-Core rev: a81d59bc8d13402725f0f5b42af92332570484d3) Signed-off-by: Jackie Huang <jackie.huang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* build-appliance-image: remove hardwired pathCristian Iorga2014-09-161-1/+1
| | | | | | | | | | | | | Remove wrong absolute hardwired path for the VM disk image. Fixes [YOCTO #6728]. (From OE-Core rev: f8a9b81192f8846937d85c7189018e35c860f7bd) Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-16 19:43:12 +0000