aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2018-01-07v86d: take tarball from debianAlexander Kanavin
Gentoo is removing the package due to dead upstream; Debian might carry it for a while longer. Fixes [YOCTO #12452] (From OE-Core rev: 0addd635cb0fcc51399d5b5082e6b246220d65b2) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07staging.bbclass: handle postinst-useradd-* fixmesMikko Ylinen
After 02457ef7f600ce954874e2d11e74b1c6daaa3bfc, PSEUDO for postinst-useradd-* scripts get to use only one PSEUDO_LOCALSTATEDIR which is set under recipes ${WORKDIR}. When the those scripts are run in a clean build environment that is built from the sstate (populate_sysroot_setscene run for postinst-useradd-* providers), pseudo fails to run because it cannot access the PSEUDO_LOCALSTATEDIR (recipe ${WORKDIR}s do not exist). This triggers a sysroot staging error. Previously, the PSEUDO_LOCALSTATEDIR setting in useradd.bbclass worked because the RSS sstate/staging logic automagically processed ${STAGING_DIR_TARGET} in postinst-useradd-* scripts to point under the sysroot being built. The fix uses the same fixme processing by adding PSEUDO_LOCALSTATEDIR variable to it. Furthermore, LOGFIFO is added to be able to use the logging fifo of the recipe that actually runs postinst-useradd-*. (From OE-Core rev: 764b93cac374a55c31c86627f13270db874cdbdb) Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07runqemu: Add workaround for APIC hang on pre 4.15 kernels on qemux86Richard Purdie
On pre 4.15 host kernels, an APIC window emulation bug can cause qemu to hang. On 64 bit we can use the x2apic, for 32 bit, we just have to disable the other timer sources and rely on kvm-clock. [YOCTO #12301] (From OE-Core rev: 6a2bdae1c418374aee9b53abfc03cb506647c94e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 82e67b82ea8e12aa0b7b9db1d84fec0436dec71b) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07cross.bbclass: Remove usage of host flags for cross-compilationNikolay Merinov
BUILD_* flags can't be used as TARGET_* flags even for "cross" packages. gcc-cross buils leaks config.log's through "gcc-stashed-builddir" and TARGET_* flags to libgcc cross-build through "gcc/libgcc.mvars" file on "gcc-stashed-builddir". This means that if BUILD_CFLAGS contains host-specific flags like "-isystem/usr/include" libgcc build will fail "do_qa_configure" and "do_package_qa" checks. Remove host-related flags from TARGET_* flags for gcc-cross build. (From OE-Core rev: 6c52b2db3a7c07a7bf448ba2c9db89a7734e4b4b) (From OE-Core rev: 39fcca60f64bc6afc57943881bec5641820d3d7d) Signed-off-by: Nikolay Merinov <n.merinov@inango-systems.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07bluez5: fix out-of-bounds access in SDP server (CVE-2017-1000250)Ross Burton
All versions of the SDP server in BlueZ 5.46 and earlier are vulnerable to an information disclosure vulnerability which allows remote attackers to obtain sensitive information from the bluetoothd process memory. This vulnerability lies in the processing of SDP search attribute requests. (From OE-Core rev: d25716ceb3ffcdfcfa54516596bd94bf5c050bac) (From OE-Core rev: c8f4cd337b9cc5c5c3fc40c6a6d8d2394fdc9ea3) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver: preserve sysroot paths in configured modeRoss Burton
do_ar_configured alters WORKDIR but also expects to be able to run do_configure, so forcibly expand the paths to the sysroots as otherwise they'll point to a non-existant directory in the temporary WORKDIR. [ YOCTO #11584 ] (From OE-Core rev: aa2240657b015d46e9ba4bcb6264709a82313d83) (From OE-Core rev: cd5e6172525c7618e93d8255a1d6102a24496f53) (From OE-Core rev: 60f2c790d5e83c1a55d7a40b32a7cef6a5a5eab6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver: avoid archiving source for glibc-localeZhenbo Gao
Avoid archiving source for glibc-locale as its tasks do_fetch do_unpack and do_patch have already been deleted. (From OE-Core rev: 50ed224ebc8d88a900febdc78013fa0c791d71cf) (From OE-Core rev: 32a332a54e8b857668eb60e36152b8d2ecec15bf) (From OE-Core rev: 23d55b31272568ce7d8b4549381c31512ff93b6a) Signed-off-by: Zhenbo Gao <zhenbo.gao@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver.bbclass: adapt do_unpack_and_patch to RSSMikko Ylinen
do_unpack_and_patch was not correctly run until recently ("archiver.bbclass: various fixes for original+diff mode") but with the fix applied, the errors we get indicate the function is not adapted to work with recipe specific sysroots. do_unpack_and_patch sets WORKDIR to ARCHIVER_WORKDIR which affects all path settings relative to WORKDIR, inluding the paths to recipes' sysroots. IOW, when do_unpack and do_patch are run, they cannot find the necessary native tools and files located in the sysroot (e.g., quiltrc) because the paths point to ARCHIVER_WORKDIR. Adapt do_unpack_and_patch to RSS by restoring the original STAGING_DIR_NATIVE after WORKDIR is changed to ARCHIVER_WORKDIR. (From OE-Core rev: db7d2cc5a4df3c2077ba874c7ae395c73fd9ed13) (From OE-Core rev: 7c0e3c5fa39e7ed3eedee8bac206476f70d1f422) (From OE-Core rev: adb5234ac9c96f29336397552176ab5086772069) Signed-off-by: Mikko Ylinen <mikko.ylinen@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver.bbclass: fix do_ar_original error for matchbox-desktopDengke Du
Error: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ERROR: matchbox-desktop-2.1-r0 do_ar_original: Can not determine archive names for original source because 'name' URL parameter is unset in more than one URL. Add it to at least one of these: git://git.yoctoproject.org/matchbox-desktop-2 file://vfolders/%2A ERROR: matchbox-desktop-2.1-r0 do_ar_original: Function failed: do_ar_original ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In function do_ar_original, when recipes have more than one source, it added the "name" URL parameter as suffix to identify the created tarball. But the URL type "file://" that we always used to represent a series of patches, it didn't have "name" parameter, so it failed. So set "name" to the folder name to identify the created tarball, for example: In matchbox-desktop bb file, the SRC_URI contains: file://vfloders/* We set "name" to "vfolders" to identify the created tarball. In connman-gnome bb file, the SRC_URI contains: file://images/* We set "name" to "images" to identify the created tarball. (From OE-Core rev: 0af636c635391b30c987dedeffe597ef4f8a1ed8) (From OE-Core rev: 9dd945d083ee742dcb75d24d4be40468121008a6) (From OE-Core rev: 113de7ab1e61997147b4b292b7de162d44296d59) Signed-off-by: Dengke Du <dengke.du@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver.bbclass: do not cause kernel rebuildsPatrick Ohly
Adding or removing archiver.bbclass from a build configuration causes rebuilds of linux-yocto-based kernels because of the do_kernel_configme->do_unpack_and_patch task dependency. This particular dependency can be ignored for the do_kernel_configme sstate signature calculcation. Idea for the fix from Richard Purdie. Note that building the kernel and adding archiver.bbclass later to archive sources leads to do_unpack_and_patch running after do_kernel_configme (because that already ran in the first build), which might be problematic. This is independent of the change here. The use case in YOCTO #11441 is to removed archiver.bbclass between a production build with archiving enabled and builds via oe-selftests without archiving. That direction is fine. Fixes: YOCTO #11441 (From OE-Core rev: fed0ed82928e6a7846fbad233ac657bd17bcefc7) (From OE-Core rev: 201c634946d07c8d0ab6d486e5031b4479eb6707) (From OE-Core rev: 81a6623592c3c496b16f0dc2c0ad04c16b0baf29) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver.bbclass: various fixes for original+diff modePatrick Ohly
The diff.gz gets created in do_unpack_and_patch, but do_deploy_archives did not depend on it, so there was a race condition. For example, "bitbake linux-intel:do_deploy_archives" without a prior "bitbake linux-intel:do_kernel_configme" did not deploy the diff.gz. When do_unpack_and_patch ran first, it failed because the output directory didn't exist yet and the error was not detected because the result of the diff command wasn't checked. Changing the current working directory in create_diff_gz() without returning to the original directory caused warnings like this: WARNING: linux-intel-... do_unpack_and_patch: Task do_unpack_and_patch changed cwd to .../tmp-glibc/work-shared/intel-corei7-64 (From OE-Core rev: 18aac553ca35049c80b6cc82ff0e69ce8a7a03a9) (From OE-Core rev: 58ae2be68c2eb4153c09386eebefe9b57400c777) (From OE-Core rev: 497795c5a9db8ddb29302780a94eabf6f9b05c9d) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver.bbclass: enhance do_ar_recipe task signaturePatrick Ohly
Previously, do_ar_recipe ran again unnecessarily when adding or removing classes like buildhistory.bbclass, because that changes the BBINCLUDED variable which do_ar_recipe uses to find .bbappend files. This is both extra work and also sometimes triggered "basehash changed" errors (seen under oe-selftest, which adds machine.inc and bblayers.inc) because BBINCLUDED is special and does not cause the basehash to be recalculated. The file *content* already was not considered in the task signature, instead relying indirectly on PF (which includes the revision assigned by a PR server) to ensure that a new versioned source archive gets created each time there is a rebuild. Therefore it makes sense to use the same mechanism and also ignore the file *list*, i.e. exclude BBINCLUDED from the task signature. (From OE-Core rev: 9666f0e0b02efc14226c77497fd38f79fc372f98) (From OE-Core rev: f560bfe15d283c59094a0f7987fad10baad053b4) (From OE-Core rev: 62fbbf99de7b427d95f51d63039ab5a803209904) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07archiver: Escape recipe name in regexJoshua Watt
The recipe name needs to be escaped when using it in a regular expression so that and special characters are treated literally (From OE-Core rev: 53c8cceb744adda1bf899d62071d11b20a5dea98) (From OE-Core rev: 5818fa4ddb1473b7d951ccb24f9953a011082312) (From OE-Core rev: ed2d0781d3e991a7e0eb4bf7a04a9e91cd8793be) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07classes: drop image dependencies on TOPDIR variablePaul Eggleton
We don't need a dependency on this variable changing, and having one causes locked signature warnings during eSDK installation if you have INITRAMFS_IMAGE_* set (since TOPDIR will always be different between the eSDK and the environment in which it was built). Relates to [YOCTO #12102]. (From OE-Core master rev: 073610af04be326f9245ca91714526b390fb72cd) (From OE-Core rev: 94a9f9a7dc5a736b7986b889895c736f02110715) (From OE-Core rev: 8bf158857d7c597c58efc4023bdd9c2785d43ad3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-07image.bbclass: drop initramfs bundle related codeMing Liu
The original purpose of this code snippet was to repackage initramfs bundled kernel images before do_image_complete, to be able to be included by rootfs, but it's not going to achieve that since the initramfs bundled kernel images are not even installed to ${D}/boot after commit a49569e3a7534779bbe3f01a0647fd076c95798d: [ kernel.bbclass: do not copy bundled initramfs to /boot ] So there is not a initramfs bundled kernel package at all, we should drop the code, because it is leading kernel do_initramfs_bundle unnecessarily rerun and it's very time consuming and hence is impacting the performance a lot. (From OE-Core master rev: eca501aeb4f2cc9255fabab14c68f6910367aaf9) (From OE-Core rev: 22fd010b71b6ce79f3ede31e4e7da9dbc72de70e) (From OE-Core rev: f549338b0ed4d53dedac84c86e70ea9ffd12a17e) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2018-01-06local.conf.sample: Weakly set BB_DISKMON_DIRSRichard Purdie
For various reasons we need to be able to set and override this from auto.conf on our test infrastructure. We have tried forcing the variable but this then breaks other selftests. In the interests of not complicating things further and needing to modify the tests across releases, weaken the default assignment. (From meta-yocto rev: 3b478600708748e9127b32d5fba8f5ec22cb981d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-22documenation: Prepared docs for a 2.3.3 point releaseScott Rifenbark
poky.ent - updated variables mega-manual.sed - replaced '2.3.2' with '2.3.3' <book>.xml - updated all the manual revision tables to use a 2.3.3 release of January 2018: (From yocto-docs rev: 375b229399f77696c742e0aa3626792a24fecff2) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-14build-appliance-image: Update to pyro head revisionRichard Purdie
(From OE-Core rev: 10a75d2f1004c4cdf3fbe850c41ff47721eb139a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-14poky: Update version to 2.3.3Richard Purdie
(From meta-yocto rev: b61638847dda679cafd1dc3031b17522c7e9b7c7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11cross-localedef-native: Include locale_t.hJoshua Watt
Newer versions of glibc (2.26) moved the struct locale definition from xlocale.h to bits/types/locale_t.h. For compatibility with build hosts using this version of glibc, include this header. See f0be25b6336db7492e47d2e8e72eb8af53b5506d in glibc (From OE-Core rev: 4e9bb9ab2e5c603f3eb2d52ce272401c8e320cc0) (From OE-Core rev: ab2bbccf9afb1db05a1f9fbcb5ec31bc1e4cb5eb) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11glibc_2.25: fix building for x86 with -Os (or -fno-omit-frame-pointer)Andre McCurdy
Glibc 2.25 fails to build for x86 when frame pointers are enabled (ie when optimised for size or when -fno-omit-frame-pointer is explicitly included in CFLAGS etc). Backport the upstream fix from glibc 2.26. https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=3b33d6ed6096c1d20d05a650b06026d673f7399a (From OE-Core rev: 81ba29c7b9c872d9a9c2efe5f9f8fe6a492af813) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11weston: add patch to set pitch correctly for subsampled texturesAndrey Konovalov
This fixes display issue with YUV420/I420 and NV12 formats, that can result in crash of weston. The master branch has this fix as part of commit 148920f3971d "weston: Bump version to 3.0.0". The patch has been rebased to apply cleanly to weston 2.0.0. (From OE-Core rev: bdf87b453867d2f74d97c0a7e0f71902a47b11fb) Signed-off-by: Andrey Konovalov <andrey.konovalov@linaro.org> Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9955Armin Kuster
Affects: <= 2.28 [v2] Fixed signed-off-by for CVE-2017-9955_9 (From OE-Core rev: ccb2651cc736a6efd7e69a5afecd6aa975ee914c) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9954Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 85ad166e6487abcd6395569e71fa81e273d47a9d) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Secuirty fix for CVE-2017-9756Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 59956de9ffd18d65c41697772e2b95da982cc803) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9755Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 2a1da95cf865de024d278178b28e58a299526121) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9753Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 02e45129712d7629bfbe3675ed8e735f66ae6301) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9752Armin Kuster
Affects: <= 2.28 (From OE-Core rev: b7bab86b9598ad0fedfcbdafb3d1fc2d522b2b70) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9751Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 6e6544eb51d8041fd939581dc2a5178db948ec4a) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11Binutils: Security fix for CVE-2017-9750Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 96e07bc43b817dbc35b8a317e801dee1974939b9) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9749Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 8b177c76ce892c1ee064498b8fa21e99a993d69e) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9748Armin Kuster
affects: <= 2.28 (From OE-Core rev: 1a60007cb6705ba25a2a6d07ccf2c2639d131874) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9747Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 2a40f61560be1db90aec08493f6c760de5b4d264) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security for fix CVE-2017-9746Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 75731517f8df241ae40378bca1b5b8ec5b45dab0) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9745Armin Kuster
Affects: <= 2.28 (From OE-Core rev: da1960fb6d9de9620ac507256554659e1bbe7083) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix for CVE-2017-9744Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 462cdbd112555a363eddfe3e47cd9b14fccf9395) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9742Armin Kuster
Affects: <= 2.28 (From OE-Core rev: f8d6efda47b993e5e27631b9b7cd0a8638178e15) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9040 and CVE-2017-9042Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 9e96e8d16590601e716ddb36194fd9642a5d1643) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9039Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 1d467814bfc36755a7a795aa3d1c4d2d2e083171) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-9038 and CVE-2017-9044Armin Kuster
(From OE-Core rev: 32e5dedd7bf5b249a8f89f88bbe17d5ba71039b7) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix CVE-2017-8421Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 7442e97d451047e5f8ed2e23f5898837a7d572a7) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix for CVE-2017-8398Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 8bbed39afd0d4197e39db587f41cd301726c2958) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Secuirty fix CVE-2017-8396 and CVE-2017-8397Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 006d106c81420ab53a9755f96edb58c227850587) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Security fix CVE-2017-8395Armin Kuster
Affects: <= 2.28 (From OE-Core rev: b6c2ce1cd3907f5c6f5dcff0afb971d000e7c9bc) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutls: Secuirty fix CVE-2017-8394Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 4684afc0f29beafc0b97a0c7f0479a88c5a69d8e) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix CVE-2017-8393Armin Kuster
Affects: <= 2.28 (From OE-Core rev: e96c9ab000c8693788b7a233bd7061d43cbe24d7) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security Fix CVE-2017-7614Armin Kuster
Affects: <= 2.28 (From OE-Core rev: 6dd4758d9f7060ccf1a30d7a4adb09beb43bc574) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11binutils: Security fix CVE-2017-7223Armin Kuster
Affects <= 2.28 (From OE-Core rev: 04ca81f0539a7549d4c527377c8a05b396247220) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11lib/oe/terminal.py: use an absolute path to execute oe-gnome-terminal-phonehomeMing Liu
A flaw was found on my Ubuntu 14.04.5 LTS, on which that gnome-terminal is the default terminal, when I run any of the tasks: bitbake busybox -c menuconfig/devshell/devpyshell bitbake virtual/kernel -c menuconfig/devshell/devpyshell I got a error as follows: "Failed to execute child process "oe-gnome-terminal-phonehome" (No such file or directory)" Seems the environment of the process calling Popen is not passed to the child process, this behaviour is a known issue in Python bug tracker: http://bugs.python.org/issue8557 It could be fixed by using an absolute path instead per test. (From OE-Core rev: 6dcafdc6754f9eda22dfe93609401d75e8626c05) Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 2117c148ef07d84bc605768e3b3671b0126b9337) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-12-11gcc: Use libssp_nonshared linker specs only for ppc/muslFlorin Sarbu
Link libssp_nonshared.a only for ppc/musl because glibc already provides the content for libssp_nonshared in libc_nonshared.a and therefore we dont need to make it universal. (From OE-Core rev: c08247e3c7c004a40281d4010186a9ace86e0e47) (From OE-Core rev: ac2aad028daca6ea3aa0c0ccea8d528e896f8349) Signed-off-by: Florin Sarbu <florin@resin.io> Signed-off-by: Armin Kuster <akuster@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-06-12 04:44:15 +0000