summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* selftest/runqemu: Handle SystemExitRichard Purdie2018-10-091-8/+11
| | | | | | | | | | | | | | | | | | | The sigchld handler in runqemu can raise a SystemExit when qemu shuts down. Rather than backtracing, accept this as a successful test result. ERROR: runqemu.QemuTest.test_qemu_can_shutdown (subunit.RemotedTestCase) testtools.testresult.real._StringException: Traceback (most recent call last): File "/home/pokybuild/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/runqemu.py", line 183, in test_qemu_can_shutdown qemu_shutdown_succeeded = self._start_qemu_shutdown_check_if_shutdown_succeeded(qemu, shutdown_timeout) File "/home/pokybuild/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/selftest/cases/runqemu.py", line 175, in _start_qemu_shutdown_check_if_shutdown_succeeded time.sleep(1) File "/home/pokybuild/yocto-worker/nightly-oe-selftest/build/meta/lib/oeqa/utils/qemurunner.py", line 100, in handleSIGCHLD raise SystemExit SystemExit (From OE-Core rev: 417245923c1c2c35a60d6db29cbe5a78548860d2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemurunner: Remove the signal handler before stopping qemuRichard Purdie2018-10-091-2/+2
| | | | | | | | | | | The qemu shutdown can race with the signal handler removal leading to confusing tracebacks on slower/loaded systems. Remove the signal handler first before shutting down. (From OE-Core rev: 1b63ce7bb83134f84bf07d1075d5ca0d5466ed3d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* strace: fix ptestsAnuj Mittal2018-10-094-28/+42
| | | | | | | | | | | | | | | | | | | | | | | | * Let automake use parallel test harness which ensures that appropriate environment variables are actually used. * Copy generated config.h as part of ptest package and define a variable in tests Makefile to control the name of target that we'd like to invoke for tests instead of relying on default value. * configure relies on tools that are not available in release tarballs resulting in warnings and failed tests. Get the required information from available files instead. * Reduces the count of failing tests to 18 from 35. The rest of tests fail or get skipped mostly because of missing syscalls. Number of tests getting skipped can probably be reduced further. Fixes [YOCTO #12948] (From OE-Core rev: dcd674181f31a12c100f91cf6a1c3f3d52b775a2) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* util-linux: Use update-alternatives for fsfreeze, nsenterMax Krummenacher2018-10-091-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | busybox may also provide a fsfreeze and nsenter implementation, so use u-a to allow installing them side by side. If one installs both, busybox and util-linux, one gets the following error (seen on a populate-sdk run): | ERROR: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, | then please place them into pkg_postinst_ontarget_${PN} (). | Deferring to first boot via 'exit 1' is no longer supported. And the coresponding do_populate_sdk extract: | ... | update-alternatives: Error: not linking ...sdk/image/usr/local/oecore-x86_64/sysroots/armv7at2hf-neon-angstrom-linux-gnueabi/usr/sbin/fsfreeze | to /bin/busybox.nosuid /bin/busybox.nosuid since ...sdk/image/usr/local/oecore-x86_64/sysroots/armv7at2hf-neon-angstrom-linux-gnueabi/usr/sbin/fsfreeze | exists and is not a link | ... (From OE-Core rev: 94e3fdff76452d3acde42b164d3ffa6b72540a40) Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* parted: use update-alternatives for partprobeMax Krummenacher2018-10-091-0/+6
| | | | | | | | | | | | | | | | | | | | | busybox may also provide a partprobe implementation, so use u-a to allow installing them side by side. If one installs both, busybox and parted, one gets the following error: | ERROR: image do_rootfs: Postinstall scriptlets of ['busybox'] have failed. If the intention is to defer them to first boot, | then please place them into pkg_postinst_ontarget_${PN} (). | Deferring to first boot via 'exit 1' is no longer supported. And the coresponding log.do_rootfs extract: | ... | update-alternatives: Error: not linking ...image/rootfs/usr/sbin/partprobe to /bin/busybox.nosuid since ...image/rootfs/usr/sbin/partprobe exists and is not a link | ... (From OE-Core rev: 99b74d1ff23ef91c84dc81ecf6437ad3bc37fb64) Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc: Remove unnecessary --with-mpfr and --with-mpc when cross compilingMike Crowe2018-10-092-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Passing --with-mpfr and --with-mpc when compiling the cross compiler appears to be at best unnecessary, and at worst can cause build failures. Firstly, the paths passed in gcc-cross-canadian are using the undefined ${layout_exec_prefix}. This results in configure passing -I${STAGING_DIR_HOST}/include twice to the compiler when it's doing its test builds. This is mostly pointless since that directory doesn't exist with the default oe-core configuration - the correct path would be -I${STAGING_DIR_HOST}/usr/include. The path for mpfr passed in gcc-cross is correct, but unnecessary since it is just the sysroot default. I've gone back through the history, and it seems that these lines (or similar ones) were originally added way back in 8800d8be25295dd7c7d84dde62c3be4df8e43346 for GCC 4.1.1 in 2006! I asked[1] if anyone knew why this was necessary but received no response, so I can only assume that no-one knows. I've successfully built for various targets with this patch applied and observed no problems. [1] http://lists.openembedded.org/pipermail/openembedded-core/2018-September/155971.html (From OE-Core rev: 2f9f02d5fda9884ccf9ae22ceb00d59b99036a49) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rootfs_*: Also depend on do_package_qaTom Rini2018-10-093-3/+3
| | | | | | | | | | Make sure that we don't create images that have QA problems with their package files by adding do_package_qa to do_rootfs[recrdeptask]. (From OE-Core rev: 4ee2f87f0c9540c7e2c866dbc9739e21a618bddf) Signed-off-by: Tom Rini <trini@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-utils: Add support for pigzMike Crowe2018-10-092-0/+52
| | | | | | | | | | | | Support explicit use of pigz when compressing the package contents by setting: OPKGBUILDCMD = "opkg-build -Z pigz" (From OE-Core rev: 631e7bb7d02ca9cb9cb66e6b8395b197525cda55) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libgcrypt: Add the LICENSES file to LIC_FILES_CHKSUMPeter Kjellerstedt2018-10-091-1/+2
| | | | | | | | | | | | The LICENSES file contains references to source files with other licenses than GPL/LGPL that stipulate that they shall be mentioned in any documentation accompanying a product including this library. License-Update: Add missing LICENSES file (From OE-Core rev: 67bc0b3babd922c800a03c1370d6d33a75f273c1) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glib-2.0: Include the complete license information for pcrePeter Kjellerstedt2018-10-091-2/+1
| | | | | | | | | | | | | | | | | For some reason, the copyright part was left out of the license information for pcre in LIC_FILES_CHKSUM, preventing it from being used in, e.g., documentation to satisfy the requirements of the license. Also drop pcre/COPYING from LIC_FILES_CHKSUM as it does not really contain any licensing information, it only refers to a LICENSE file that does not exist. License-Update: Include the complete license information for pcre (From OE-Core rev: 2f5a7e7a04cbdc75d1b9607903889b1fd6c5e1ba) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bzip2: Include the complete license informationPeter Kjellerstedt2018-10-091-1/+1
| | | | | | | | | | | | | For some reason, the copyright part was left out of the license information included in LIC_FILES_CHKSUM, preventing it from being used in, e.g., documentation to satisfy the requirements of the license. License-Update: Include the complete license information (From OE-Core rev: ec3eb678b15d91a450adf82f38e1c1d6d81fed9b) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* curl: Include the complete license informationPeter Kjellerstedt2018-10-091-1/+1
| | | | | | | | | | | | | For some reason, the copyright part was left out of the license information included in LIC_FILES_CHKSUM, preventing it from being used in, e.g., documentation to satisfy the requirements of the license. License-Update: Include the complete license information (From OE-Core rev: 390becd2dcf4fe791ec3715a74e34a46bd457e7a) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: fix symlinksAchille Fouilleul2018-10-091-3/+3
| | | | | | | | | | | | | | | | | For nativesdk, symlinks created by do_install contain ${SDKPATHNATIVE}. This is a problem with SDKs that include nativesdk-binutils and nativesdk-gcc. When extracting such an SDK dangling symlinks are created, because relocate_sdk.py does not adjust symlinks. As a result gcc ends up calling the host binutils. Use the os.path.relpath function to obtain shorter relative paths, which do not contain ${SDKPATHNATIVE}. (From OE-Core rev: 3d6372aa2d9f752eac0e4943d1bde04f0f1924a0) Signed-off-by: Achille Fouilleul <achille.fouilleul@gadz.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* x264: Disable asm on musl/x86Khem Raj2018-10-091-0/+1
| | | | | | | | | | | | | | Fixes WARNING: x264-r2854+gitAUTOINC+e9a5903edf-r0 do_package_qa: QA Issue: ELF binary '/mnt/a/yoe/build/tmp/work/i586-yoe-linux-musl/x264/r2854+gitAUTOINC+e9a5903edf-r0/packages-split/x264/usr/lib/libx264.so.152' has relocations in .text [textrel] WARNING: x264-r2854+gitAUTOINC+e9a5903edf-r0 do_package_qa: QA Issue: ELF binary '/mnt/a/yoe/build/tmp/work/i586-yoe-linux-musl/x264/r2854+gitAUTOINC+e9a5903edf-r0/packages-split/x264-bin/usr/bin/x264' has relocations in .text [textrel] (From OE-Core rev: ea1204c6d9a02f0e38cf616e89d46530908972bb) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ffmpeg: use bfd linker always for x86 targetKhem Raj2018-10-091-0/+4
| | | | | | | | | | gold crashes when linking, so use bfd linker here, another option is to use --disable-asm but then we loose performance. (From OE-Core rev: 4015f3279aaced1c5d9ae8a6e666c9fba42558df) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ltp: recent glibc calls syscall directlyHongzhi.Song2018-10-092-0/+76
| | | | | | | | | | | | | | | | | The case of sigwaitinfo related to sigwaitinfo API failed. glibc commit 8b0e795aaa44 ("Simplify Linux sig{timed}wait{info} implementations") changed sigwaitinfo to call sigtimedwait, which calls rt_sigtimedwait syscall directly. So, an invalid pointer no longer crashes child process and test reports failure. Fix it by accepting either crash or EFAULT. (From OE-Core rev: bfd32c0d1c335e9c9cf8340f999e15054917577e) Signed-off-by: Hongzhi.Song <hongzhi.song@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: add ca-certificates to python3-crypt RRECOMMENDSRoss Burton2018-10-091-2/+1
| | | | | | | | | | | | | It's likely that the certificate root chain is needed if python3-crypt is installed, so recommend it. Also remove the redundant nativesdk-python3-crypt assignment, as the general form is sufficient when class-extended. (From OE-Core rev: dd644ee9991e953474d41dbbf713a7e33b4c9141) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libsoup: upgrade to 2.62.3Ross Burton2018-10-092-36/+3
| | | | | | | | | | | | Freeze-breaking upgrade for a security bug fix involving cookie URLs, and a number of static analysis fixes. Drop CVE-2018-12910.patch as this is merged in 2.62.3. (From OE-Core rev: a8098782fab87498026a09c06716b631c77c5ad6) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libx11: fix patch headersRoss Burton2018-10-093-3/+3
| | | | | | | | | devtool doesn't like patches without subjects, so add meaningful subjects. (From OE-Core rev: 3056a2e5d8b7e7285fd9680073a5ab613a4066e4) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: update patch statusRoss Burton2018-10-081-1/+1
| | | | | | | | | These patches are all upstream now, so mark as Backport. (From OE-Core rev: 9a84114a279000329c2878a35f197a09217cd1fc) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lib11: fix patch headersRoss Burton2018-10-083-3/+6
| | | | | | | (From OE-Core rev: 7d74f204acf6e56249f843f99927966017d4b405) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: fix patch headersRoss Burton2018-10-081-0/+3
| | | | | | | (From OE-Core rev: 46bc904bf9cf3b2a01de0ba140b31066f90bfa49) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: fix patch headersRoss Burton2018-10-081-3/+1
| | | | | | | (From OE-Core rev: 5aba4b7540a71908a5e1086f444b2f205ba5829d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdb: fix patch headersRoss Burton2018-10-081-11/+11
| | | | | | | (From OE-Core rev: cf634b35e866daacb427ab4c10d5adadaac3718b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libusb: ptest: don't skip debug output and fix failures processingMaksym Kokhan via Openembedded-core2018-10-081-9/+23
| | | | | | | | | | | | | Current run-ptest script prints nothing, when stress tests fail. Fix it in new implementation, discarding external dependency on sed. Also leave in place all stress output, just add standard ptest result. Fixes: 3f0106bf2e41 ("libusb: Add ptest") (From OE-Core rev: cd05029c78dea48c20f9acb2c5fee56b19193f22) Signed-off-by: Maksym Kokhan <maksym.kokhan@globallogic.com> Reviewed-by: Andrii Bordunov <andrii.bordunov@globallogic.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* externalsrc.bbclass: Set BB_DONT_CACHE for non-target recipesOla x Nilsson2018-10-081-2/+2
| | | | | | | | | | | BB_DONT_CACHE was not set for non-virtual recipes where PN != BPN, such as quilt-native. Recipes that do not set BBCLASSEXTEND should always have BB_DONT_CACHE set by externalsrc. (From OE-Core rev: 4eff427a0ee629a1541a420a9591411648569a97) Signed-off-by: Ola x Nilsson <olani@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* piglit: inherit pkgconfigPascal Bach2018-10-081-1/+1
| | | | | | | | | | The CMakeLists.txt of piglit uses pkgconfig internally. This makes sure pkgconfig-native is available in any case. (From OE-Core rev: ac8f27b441b9e8cee969e06e22759d49e05e1b11) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* piglit: correctly find wayland include dirsPascal Bach2018-10-082-0/+33
| | | | | | | | | | Builds include host /usr/include as the wrong wayland variable was used. The issue only surfaces if CMAKE_SYSROOT is properly set. (From OE-Core rev: d4b942c97831f6717b34caaaf2402efdffa227ba) Signed-off-by: Pascal Bach <pascal.bach@siemens.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: add mcf5441x cpu type tuningAngelo Dureghello2018-10-081-0/+13
| | | | | | | | | This patch adds tuning for the mcf5441x ColdFire family. (From OE-Core rev: 89e7192b607361769c03b939437c9815672ceadb) Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* conf/machine/include: add m68k architecture definitionsAngelo Dureghello2018-10-081-0/+8
| | | | | | | (From OE-Core rev: 475ca28ab1b42fc0307669edae220afb97dd15c3) Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kernel-arch.bbclass: add m68k to kernel arch mapAngelo Dureghello2018-10-081-0/+1
| | | | | | | (From OE-Core rev: 69be35a58ce4122763c833e13cdbcc8e7fb9c52d) Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* siteinfo: define data for m68kAngelo Dureghello2018-10-081-0/+1
| | | | | | | (From OE-Core rev: d8c2a5fa7d59580dd70b7ec57450e3b7c9a7d048) Signed-off-by: Angelo Dureghello <angelo@sysam.it> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: fix failing ssl testsAnuj Mittal2018-10-086-1/+292
| | | | | | | | | | | | | Backport two and pick some other in-review patches from Ubuntu to fix ssl test failures because of OpenSSL 1.1.x changes. Fixes [YOCTO #12788] (From OE-Core rev: 4f4bbb936231dd30c3745ef573993f1062937ffd) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: add bzip2 to ptest RDEPENDSAnuj Mittal2018-10-041-1/+1
| | | | | | | | | | A lot of tests in e2fsprogs-ptest package expect bzip2 to be present. (From OE-Core rev: fb837f11c7a7777c0c9747309f5eabf881e8f4ee) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs: fix stray quote in test configurationAnuj Mittal2018-10-041-4/+15
| | | | | | | | | | | | Introduced during the last recipe upgrade and was causing tests to fail. Fixes [YOCTO #12946] (From OE-Core rev: 1771cf07c88c27e8cf473b7f1da03db22d94837e) Signed-off-by: Anuj Mittal <anuj.mittal@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libxml2: refresh CVE-2017-8872Ross Burton2018-10-041-23/+50
| | | | | | | | | | | The patch associated with the CVE-2017-8872 report was never merged into libxml2, but a slightly different patch for the same problem was. Cherry-pick that as a backport, which also fixes the failing test suite. (From OE-Core rev: 512869aea6dde1bb2374601f7c4d793ac9edaa42) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* os-release: avoid multilib expandKai Kang2018-10-041-1/+1
| | | | | | | | | | Add os-release to NON_MULTILIB_RECIPES in multilib.conf that do not do multilib expand for os-release. (From OE-Core rev: 361382ca16c276e1e404eab58c0956a2b6d23d7e) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libcheck: avoid multilib install file conflictKai Kang2018-10-042-1/+21
| | | | | | | | | | | | The first line of output of '$CC --version' is written to check_stdint.h as a comment line. It causes multilib install file conflict. Do not echo compiler version info to check_stdint.h to fix the issue. (From OE-Core rev: f9db6ac8044495f9299fb0e962d3d6838bbce08f) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* man-db: fix multilib install file conflictKai Kang2018-10-042-1/+18
| | | | | | | | | | The first line of config file man_db.conf is the package name. It causes multilib install file conflict. So add a patch to remove the line. (From OE-Core rev: d138b1ec4aef88a3b0c4f1d698ed2a224c93b889) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cups: fix multilib install file conflictsKai Kang2018-10-042-1/+23
| | | | | | | | | | | | A comment line of conf file cups-files.conf refers to var @CUPS_SERVERBIN@ is ${libdir} related and then it causes multilib install file conflict. Remove @CUPS_SERVERBIN@ from the comment line to avoid the conflict. (From OE-Core rev: ac4df3f83fccfa7dd75d6a913b7ab75e49a7b986) Signed-off-by: Kai Kang <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa: Disable asm on muslKhem Raj2018-10-041-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Musl started blocking dlopen of libs with initial-exec references into dynamic TLS area, via https://github.com/kraj/musl/commit/5c2f46a214fceeee3c3e41700c51415e0a4f1acd prior to that commit, musl was loading it and silently letting subsequent TLS accesses via the miscompiled code clobber memory that didn't belong to them This was wrong behavior and it relied on additional space reserved by libc in TLS space to adjust fo such broken libs, but it also fails with glibc if the reserved space was already used up Right fix is that mesa should be patched to remove all the initial-exec hacks and use real TLS, and -mtls-dialect=gnu2 (TLSDESC) should be used on archs it's supported on (i386, x86_64, and aarch64) to make up for the lost performance, but mesa hardcodes the initial-exec, so there must be a reason that probably is better known to mesa devs. but we 'fixed' it for musl by adding --disable-glx-tls for mesa in OE, which uses pthread_getspecific instead and makes is lot slower. this caused additional problems with security flags on, it get textrels in .text segment. Therefore this is 'second fix' to get us through this warning. Cause is some unknown part of mesa's x86 assembly code is broken by readonly text segments [ YOCTO #12918 ] (From OE-Core rev: 27c25de38aacc98fe376422bbbee417b2b45a98e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pango: respect PTEST_ENABLEDRoss Burton2018-10-041-1/+1
| | | | | | | | | | Don't use the 'ptest' DISTRO_FEATURE because whilst that can be on, PTEST_ENABLED could have been overwritten. (From OE-Core rev: 57e41b6178bf1d88a901cda862e3e054148e86ac) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pango: don't disable debuggingRoss Burton2018-10-041-2/+0
| | | | | | | | | | | | | By explicitly disabling debugging we get *no* safety checks: the GLib asserts and checks are all disabled. This is fine for absolute performance but something that should be opt-in. This also breaks the test suite, which relies upon the asserts to work. (From OE-Core rev: 191f7e2b2fe09ff3276efb68ca91c853291d41f8) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* connman: neaten patchesRoss Burton2018-10-042-9/+11
| | | | | | | | | | | The upstreamable include-tweaking patches contained fragments that should be in the not-upstreamable musl-specific res_ninit replacement, so move them to the right patch. (From OE-Core rev: 18fd5bc97e6b061eec4be0738f20fcbace6bdafe) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-packagegroup-sdk-host.bb: remove nativesdk-dnfChen Qi2018-10-041-1/+0
| | | | | | | | | | | | | | | | | Currently the dnf command inside SDK does not work. We will get error message like below: ImportError: No module named 'dnf' So remove it from nativesdk-packagegroup-sdk-host, otherwise, users will get unpleasant experience if they are working inside SDK environment on some distros like Fedora. (From OE-Core rev: a7005a4fc5f29db796b1d258b7c259b9433848ce) Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* openssl: skip ptest case `test_symbol_presence'Hongxu Jia2018-10-042-0/+47
| | | | | | | | | | | | | The case in ptest use `nm -Pg libcrypto.so' to check symbol presence, if library is stripped or debug split, the case will fail. The test case needs debug symbols then we just disable that test. (From OE-Core rev: 28d3a4cb1ffb508018faebf088eabfd14bcf3113) 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>
* elfutils: fix CVE-2018-16403 & CVE-2018-16402Hongxu Jia2018-10-043-0/+145
| | | | | | | | (From OE-Core rev: a7c3c897d2cbe7e473a7fb057a3f74ebc9e04023) 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>
* nativesdk-bison: Add to nativesdk-packagegroup-sdk-host and set BISON_PKGDATADIRHe Zhe2018-10-042-0/+5
| | | | | | | | | | | bison is needed when building kernel. Add it to nativesdk-packagegroup-sdk-host and set BISON_PKGDATADIR for bison to use its components. (From OE-Core rev: 8aa27e4eb2f08281329ca1a1da421c6fc376bc8d) Signed-off-by: He Zhe <zhe.he@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtiff: fix CVE-2017-17095Joe Slater2018-10-042-0/+47
| | | | | | | | | | | Backport fix from gitlab.com/libtiff/libtiff. nvd.nist.gov does not yet reference this patch. (From OE-Core rev: f72c8af3f2c1ec9e4d9ffcf0cc6e7fdf572b21b9) Signed-off-by: Joe Slater <joe.slater@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* glibc: Fix glibc reproducibility issuesRichard Purdie2018-10-042-0/+260
| | | | | | | | | | | | | Currently for non-IA platforms, glibc is not reproducible as host system paths are being injected into target binaries. These spread through all target binaries on the system which link to the libc. Add a patch which injects .file directives into the assembly pieces and works around this issue until a better solution can be found. (From OE-Core rev: 4d6fd8178da75f9a1870db290bbe24de5af752c9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>