aboutsummaryrefslogtreecommitdiffstats
path: root/meta
AgeCommit message (Collapse)Author
2016-02-02linux-yocto: Update SRCREV for qemux86* for 4.1, fixes CVE-2016-0728hsalejandro/jethrokernelAlejandro Hernandez
This addresses CVE-2016-0728: KEYS: Fix keyring ref leak in join_session_keyring(), and upgrades to LINUX_VERSION 4.1.17 Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
2016-02-02linux-yocto: Update SRCREV for qemux86* for 3.19, fixes CVE-2016-0728Alejandro Hernandez
This addresses CVE-2016-0728: KEYS: Fix keyring ref leak in join_session_keyring() Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
2016-02-02linux-yocto: Update SRCREV for qemux86* for 3.14, fixes CVE-2016-0728Alejandro Hernandez
This addresses CVE-2016-0728: KEYS: Fix keyring ref leak in join_session_keyring(), and upgrades to LINUX_VERSION 3.14.39 Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
2016-01-21nativesdk-buildtools-perl-dummy: Bump PRRichard Purdie
Recent changes to this recipe caused automated PR increments to break, regressing package feeds. The only way to recover is to bump PR, so do this centrally to fix anyone affected. (From OE-Core rev: dacdb499d31cb2e80cca33cba9d599c8ee983dc4) (From OE-Core rev: 8ce8f62b22b1e20db0f62d7bd8246738147d5f2e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-21nativesdk-buildtools-perl-dummy: properly set PACKAGE_ARCHPaul Eggleton
Turns out I did a silly thing in OE-Core revision 9b1831cf4a2940dca1d23f14dff460ff5a50a520 and forgot to remove the explicit setting of PACKAGE_ARCH outside of the anonymous python function; the original bug was apparently fixed but the functionality of allarch.bbclass was being disabled because it was able to see that PACKAGE_ARCH was not set to "all" - which was what I was trying to ensure. (From OE-Core rev: a25ab5449825315d4f51b31a634fe6cd8f908526) (From OE-Core rev: afd527d365c58e622983b77a1a7ed57f59ef7b32) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-21nativesdk-buildtools-perl-dummy: fix rebuilding when SDKMACHINE changesPaul Eggleton
This recipe produces an empty dummy package (in order to satisfy dependencies on perl so we don't have perl within buildtools-tarball). Because we were inheriting nativesdk here the recipe was being rebuilt, but having forced PACKAGE_ARCH to a particular value the packages for each architecture were stepping on eachother. Since the packages are empty they can in fact be allarch (even though they won't actually go into the "all" package feed). It turns out that nheriting nativesdk wasn't actually necessary either, so drop that. Fixes [YOCTO #8509]. (From OE-Core rev: 9b1831cf4a2940dca1d23f14dff460ff5a50a520) (From OE-Core rev: 66694fe312cf0668d08e42246332ce085a4d6372) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-20Revert "gstreamer1.0-plugins-good.inc: add gudev back to PACKAGECONFIG"Richard Purdie
This reverts commit 5c90b561930aac1783485d91579d313932273e92. The original change was intentional so back out 'fixes'. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-20Revert "gstreamer: Deal with merge conflict which breaks systemd builds"Richard Purdie
This reverts commit bc458ae9586b45b11b6908eadb31e94d892e698f. The original change was intentional so back out 'fixes'. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-17build-appliance-image: Update to jethro head revisionRichard Purdie
(From OE-Core rev: 716d3140c150bb3d99210e74da91904efc84c907) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-17gstreamer: Deal with merge conflict which breaks systemd buildsRichard Purdie
In jethro, the dependency is "udev", the change to libgudev happened in master after the release and this was a mistake during backporting of gstreamer fixes. (From OE-Core rev: bc458ae9586b45b11b6908eadb31e94d892e698f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15build-appliance-image: Update to jethro head revisionRichard Purdie
(From OE-Core rev: bc1d59a075bfd1b0dca7a19553cc7970b7460b38) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15kernel/kernel-arch: Explicitly mapping between i386/x86_64 and x86 for ↵Jianxun Zhang
kernel ARCH For a bare-bone kernel recipe which specifies 32 bit x86 target, a 64 bit .config will be generated from do_configure task when building 32-bit qemux86, once all of these conditions are true: * arch of host is x86_64 * kernel source tree used in build has commit ffee0de41 which actually chooses i386 or x86_64 defconfig by asking host when ARCH is "x86" (arch/x86/Makefile) * bare-bone kernel recipe inherits directly from kernel without other special treatments. Build will fail because of the mismatched kernel architecture. The patch sets ARCH i386 or x86_64 explicitly to configure task to avoid this host contamination. Kernel artifact is also changed so that it can map i386 and x64 back to arch/x86 when needed. (From OE-Core rev: 6ffcfc0bc08bcbe81e17ceeb7094f09cc9214b94) Signed-off-by: Jianxun Zhang <jianxun.zhang@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15openssh: update to 7.1p2Alexander Kanavin
This fixes a number of security issues. (From OE-Core rev: b31fc9b167e5ca3115a0d0169126d63f2dbd3824) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15classes/populate_sdk_ext: disable signature warningsPaul Eggleton
The user of the extensible SDK doesn't need to see these. (From OE-Core master rev: 7045fabf73d4eef9c023edb9e0a8b8d1d3f04680) (From OE-Core rev: f89d5dc8e980e1ac48357f49158632689582d7fb) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15classes/populate_sdk_ext: fix cascading from preparation failurePaul Eggleton
During extensible SDK installtion, if the build system preparation step fails we try to put something at the end of the environment setup script to show an error when it is sourced, in case the user doesn't realise that the partially-installed SDK is broken. However, an apostrophe in the message (actually a single quote) appears to terminate the string and therefore breaks the command. Drop it to avoid that. (From OE-Core master rev: 21e591d182e24c399ae010a8eff9b89947061a46) (From OE-Core rev: 91326ede91ff7b820ec60ec642927cc223cae81f) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15buildhistory: fix not recording SDK informationPaul Eggleton
After OE-Core revision baa4e43a29e45df17eaa3456acc179b08d571db6 we lost recording SDK the contents in buildhistory. This was due to the SDK_POSTPROCESS_COMMAND variable being set with = in populate_sdk_base.bbclass which overwrote any value set with += in buildhistory.bbclass; to fix it, use _append in buildhistory.bbclass instead. Fixes [YOCTO #8839]. (From OE-Core master rev: 11d1aa82ef4a00051e0a50a87a1efed1c50c73b5) (From OE-Core rev: 36d4b0903890bc793608759b3351a5de4229de11) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15classes/populate_sdk_ext: error out of install if buildtools install failsPaul Eggleton
If the installation of buildtools fails then we should fail the entire installation instead of blindly continuing on. (From OE-Core master rev: 34bb63e6c72fb862e0ef0d2b26e1bfddaf7ddb99) (From OE-Core rev: 696979ef39fbd85fa74cfb4a0cbee49b045e2d92) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-15gstreamer1.0-plugins-good.inc: add gudev back to PACKAGECONFIGRobert Yang
The 66e32244aed8d33f1b49fbe78179f2442545c730 wrongly removed gudev from PACKAGECONFIG, now add it back. (From OE-Core rev: 5c90b561930aac1783485d91579d313932273e92) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libaio: don't disable linking to the system librariesRoss Burton
For some reason that I don't understand (a decade-old attempt at optimisation?) libaio disables linkage to the system libraries. Enabling fortify means linking to the system libraries, so remove the existing addition of -lc for x86 (the problem also happens on at least PPC) and just link to the system libraries on all platforms. Also remove the sed of src/Makefile as the build not respecting LDFLAGS has been fixed upstream. (From OE-Core rev: f435ac9db0581d8313a38d586b00c2b3de419298) (From OE-Core rev: 901af5a00338fd8f1ace939123484ea91c090a7a) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14linux-yocto/4.1: update to v4.1.15Bruce Ashfield
Updating the 4.1 kernel repo to the latest 4.1.x stable. (From OE-Core rev: 1df3a79cf454754e6be6c1ffc91ba8310a880616) (From OE-Core rev: 1896042df8db8ec21e41d45c2640360242fb0aee) Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-5312Armin Kuster
(From OE-Core rev: 8546fada29f2c8ec0111a15fe50d90d3f2518d52) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-8242Armin Kuster
(From OE-Core rev: d392edafa1d73cace437f45bfbc147de9fc4cf8b) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-7500Armin Kuster
includes a depend fix security issue CVE-2015-7500 (From OE-Core rev: 2febaf28b165dadc23eeb7f16391e72d4184b0a7) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-7499Armin Kuster
includes: CVE-2015-7499-1 CVE-2015-7499-2 (From OE-Core rev: 51aedd5307b92b63d97b63bd9911eda67ee6fde8) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-7497Armin Kuster
(From OE-Core rev: c1d69a59a693dabf4b48619fdc12ce0f148a2386) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-7498Armin Kuster
(From OE-Core rev: cece10f44c9cceddab17adf1a1debc4b14e50a8d) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-8035Armin Kuster
(From OE-Core rev: 1266b6269cbafbb529579d92334785a833c22fc1) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-7942Armin Kuster
includes: CVE-2015-7942 CVE-2015-7942-2 (From OE-Core rev: 66c7e97f8687c1b656c322282ee7cdc200945616) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-8317Armin Kuster
(From OE-Core rev: 42086e309dfce3caa05e88681875f5f78cf5f095) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14libxml2: security fix CVE-2015-7941Armin Kuster
includes: CVE-2015-7941-1 CVE-2015-7941-2 (From OE-Core rev: 48af957147a091550c089423e3a65bac6596c41e) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14openssl: fix for CVE-2015-3195Armin Kuster
(From OE-Core rev: 85841412db0b1e22c53e62a839d03f7672b07b64) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14openssl: fix for CVE-2015-3194Armin Kuster
(From OE-Core rev: ce9f78296101772655809036e21009acec78da24) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-14openssl: fix for CVE-2015-3193Armin Kuster
(From OE-Core rev: 4d9006b1217ee7e97108f36db19aebd93e1d9850) Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12logrotate: do not move binary logrotate to /usr/binHongxu Jia
In oe-core commit a46d3646a3e1781be4423b508ea63996b3cfca8a ... Author: Fahad Usman <fahad_usman@mentor.com> Date: Tue Aug 26 13:16:48 2014 +0500 logrotate: obey our flags Needed to quiet GNU_HASH warnings, and some minor fixes. ... it explicitly move logrotate to /usr/bin without any reason, which is against the original Linux location /usr/sbin. So partly revert the above commit which let logrotate be kept in the original place /usr/sbin. (From OE-Core master rev: 0007436b486fd0bea9e6ef60bf57603e7cfce54b) (From OE-Core rev: c0a13c410393ce51a2a55e36a0913c0136058bdc) Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12cairo: fix license for cairo-script-interpreterAndre McCurdy
Without an explicit license, cairo-script-interpreter inherits the default LICENSE and isn't packaged in builds which blacklist GPLv3. (From OE-Core master rev: cb8f84218b065fed88a8c36f3c78065e8ab726bf) (From OE-Core rev: 6d0cf8ebde4eaa2c868dac8d0dac498c4210ec05) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12glibc: Fix ld.so / prelink interface for ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATAMark Hatle
A bug in glibc 2.22's ld.so interface for the prelink support causes the displayed values to be incorrect. The included path fixes this issue. Clear ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA for prelink prelink runs ld.so with the environment variable LD_TRACE_PRELINKING set to dump the relocation type class from _dl_debug_bindings. prelink has the following relocation type classes: where ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA has a conflict with RTYPE_CLASS_TLS. Since prelink doesn't use ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA, we should clear the ELF_RTYPE_CLASS_EXTERN_PROTECTED_DATA bit when the DL_DEBUG_PRELINK bit is set. (From OE-Core master rev: 12c86bdcc60c54e587a896b0dceb8bb6cc9ff7e3) (From OE-Core rev: 73919830f88f2d28da973e72fbdfaab591a5af69) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12gcc: Update default Power GCC settings to use secure-pltMark Hatle
The gcc default, bss-plt, will cause errors when using the prelinker. All other distributions that I am aware of are using the the secure-plt. For an explanation of the differences, the gcc docs: Current PowerPC GCC accepts a `-msecure-plt' option that generates code capable of using a newer PLT and GOT layout that has the security advantage of no executable section ever needing to be writable and no writable section ever being executable. PowerPC ld will generate this layout, including stubs to access the PLT, if all input files (including startup and static libraries) were compiled with `-msecure-plt'. `--bss-plt' forces the old BSS PLT (and GOT layout) which can give slightly better performance. The security of the new PLT and ability to run the prelinker outweigh any performance penalty. The secure-plt is enabled by default. The old bss-plt can be enabled by selecting 'bssplt' in the DISTRO_FEATURES. (From OE-Core master rev: 70c55aada1101a5c687cdaa79f370fa4530b39d9) (From OE-Core rev: 44adc575be5d9b9ad0d87e143467aeeadde2fe89) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12prelink: Fix various prelink issues on IA32, ARM, and MIPS.Mark Hatle
Fix the following issues: IA32 / ARM - Resync to glibc-2.22, fix a mismatch w/ glibc's ld.so MIPS - Ignore the new SHT_MIPS_ABIFLAGS ARM - Fix missing ARM IFUNC support chunk Also upstream prelink project no longer has a 'trunk' directory. (From OE-Core master rev: c725328f2ab5c9b220c552ed37c0d24b098a218d) (From OE-Core rev: de7f25e9d67b150db4780bb82ef9481982e81312) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12autotools: Allow recipe-individual configure scriptsJens Rehsack
OpenJDK-8 has it's configure script at common/autotools - which will cause the entire assumption of ${S}/configure is regenerated by autoreconf, intltoolize or alike fails heavily. Also - other configure mechanisms can be supported more similar (see how pkgsrc manages different ones ...) (From OE-Core master rev: fe506eddb0790e37ac1e50f37fa2e32ad81d5493) (From OE-Core rev: 809df21d8a8cc4ab860a84ccd7b2e51105df68ee) Signed-off-by: Jens Rehsack <sno@netbsd.org> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12toolchain-scripts.bbclass: unset command_not_found_handleFang Jia
On Ubuntu-system, When sourcing the env.sh from an exported sdk, and running a bogus linux command (for example "asd"), a core dump of python is usually generated. Unset the command_not_found_handle to fix it. (From OE-Core master rev: 473ccbebb426df757adb8955eaa5e191d88180d1) (From OE-Core rev: fe622c4508d2c87f7bd7c15c6391c8e1319fd3b6) Signed-off-by: Fang Jia <fang.jia@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12toolchain-shar-extract.sh: do not allow $ in paths for ext SDKPaul Eggleton
If you put an $ character in the path, SDK installation fails during the preparation stage, so add this to the disallowed characters. Fixes [YOCTO #8625]. (From OE-Core master rev: 654f4785f719552f4e78e14a5a901c07d00ce68d) (From OE-Core rev: d7bcdb33a675fbdd30596d62961be52aa98c9e05) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12toolchain-shar-extract.sh: proper fix for additional env setup scriptsPaul Eggleton
buildtools-tarball uses a custom env setup script, which isn't named the same as the default; thus unfortunately OE-Core revision a36469c97c9cb335de1e95dea5141038f337df95 broke installation of buildtools-tarball. Revert that and implement a more robust mechanism. (From OE-Core master rev: 00e081b81ba8118959b724269ba9d18d42aba8a4) (From OE-Core rev: feefaceb8a2bce8129aba82d4d93e725656ee075) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12toolchain-shar-relocate: don't assume last state of env_setup_script is goodJean-Francois Dagenais
In the case where many environment-setup-* files exist, the incorrect filename might be lastly set in env_setup_script, which leads to incorrect behaviour for the initialization of native_sysroot. The scenario I had was that our custom meta-toolchain-*.bb, which inherits populate_sdk, defined another environment-setup-* file to dump variable information for qt-creator. The file is named like so in order for the sdk shell script to pick it up and fix the SDK paths in the file. Since it (coincidentally) alphabetically comes after ...-core2, it was last set in env_setup_script and the grep OECORE_NATIVE_SYSROOT would simply be blank. The apparent symptom was "...relocate_sdk.py: Argument list too long" since the find command would not be searching in the right path. (From OE-Core master rev: a36469c97c9cb335de1e95dea5141038f337df95) (From OE-Core rev: 2f04a9285cfabdb053dafacd17320f847ac6343f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12populate_sdk_ext.bbclass: Be more permissive on the name of the buildtoolsMark Hatle
We want to support different names for the buildtools tarball. The name may not always be of the default oe-core format. For instance, at Wind River we define the built-tools name to be: ${SDK_ARCH}-buildtools-nativesdk-standalone-${DISTRO_VERSION} because thes standard SDK_NAME has additional information that is not relevant to the builtools tarball. (From OE-Core master rev: b49c6f179b06a8b97106aa4c95f2cdb3c4dc0920) (From OE-Core rev: ed92440d19e5948aa64c95fcf30b989c5e6efdb9) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12classes/populate_sdk_ext: fail if SDK_ARCH != BUILD_ARCHPaul Eggleton
The extensible SDK relies upon uninative, and with the way that uninative works, the build system architecture must be the same as the SDK architecture or the extensible SDK won't be usable. At some point in future hopefully we can remove this limitation, but until then it's disingenuous to allow this to build, so add a check to ensure SDK_ARCH == BUILD_ARCH and fail if it isn't. (From OE-Core master rev: 9e30e849eda3b0a0c54d3f7ed0102760fdaef06c) (From OE-Core rev: 1042d020d5d1b6af3f32e5fe29562d1dce765f0a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12classes/populate_sdk_ext: tweak reporting of workspace exclusionPaul Eggleton
If you have a local workspace layer enabled when building the extensible SDK, we explicitly exclude that from the SDK (mostly because the SDK has its own for the user to use). Adjust the message we print notifying the user of this so it's clear that we're excluding it from the SDK, and scale it back from a warning to a note printed with bb.plain(). (From OE-Core master rev: 90f46f74a088a7b965d2205eceb9eff6f276dd38) (From OE-Core rev: dbacd35c0db2e9f4b9b2a20ffa6bcc5f78432d8a) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12classes/populate_sdk_ext: make it clear when SDK installation has failedPaul Eggleton
When SDK preparation fails: * Insert an ERROR: in front of the error message * Add an error message to the environment setup script Hopefully this should make it more obvious when this happens. Fixes [YOCTO #8658]. (From OE-Core master rev: 105df569b3b1982005c2edb37f4690f9ba6bde35) (From OE-Core rev: 98215b9513212b7002d072afa763347520544ee0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12classes/populate_sdk_ext: tidy up preparation log file writingPaul Eggleton
Use a variable for the log file which includes the full path; this is not only neater but avoids us writing the first part (the output of oe-init-build-env) to a file in another directory since we are changing directory as part of this subshell. (From OE-Core master rev: 001af71752a9e9aab460cbd49ed049e1eb726295) (From OE-Core rev: dded5f93d5650ebe5eb661a5cec698b1fa82e1ba) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12classes/license: fix intermittent license collection warningPaul Eggleton
Fixes the following warning sometimes appearing during image builds: WARNING: The license listed ABC was not in the licenses collected for recipe xyz The files being looked for here, which runs during do_rootfs, are written out by the do_populate_lic task for each recipe. However, there was no explicit dependency between do_rootfs and all of the do_populate_lic tasks to ensure they had run - only an implicit link via do_build, so it is possible that sometimes they had not depending on how the tasks were scheduled. Add an explicit set of dependencies to fix this. (From OE-Core master rev: ef7dc532e800d9b170246550cbc8703adf624beb) (From OE-Core rev: f521d8d2d1ea495383f54e5e7c2754dde007f7eb) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-01-12classes/metadata_scm: fix git errors showing up on non-git repositoriesPaul Eggleton
Fixes the following error showing up for layers that aren't a git repo (or aren't parented by one): fatal: Not a git repository (or any of the parent directories): .git This was because we weren't intercepting stderr. We might as well just use bb.process.run() here which does that and returns stdout and stderr separately. (This was a regression that came in with OE-Core revision 3aac11076e22ac4fea48f5404110bb959547a9fe). Fixes [YOCTO #8661]. (From OE-Core master rev: f533c1bf4c6edbecc67f9e2c62fd475d64668e86) (From OE-Core rev: 8968ede9c8cdcd2cbf13bd5bba95883082189908) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-06-07 21:06:44 +0000