summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
* python3: improve reproducibilityJuro Bystricky2017-08-163-0/+99
| | | | | | | | | | | | | | | | The compiled .pyc files contain time stamp corresponding to the compile time. This prevents binary reproducibility. This patch allows to achieve binary reproducibility by overriding the build time stamp by the value exported via SOURCE_DATE_EPOCH. Patch by Bernhard M. Wiedemann. [YOCTO#11241] (From OE-Core rev: 2175aec10a764bfc925a3fb447547982d0ae662f) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* e2fsprogs-doc: binary reproducibleJuro Bystricky2017-08-162-0/+22
| | | | | | | | | | | When compressing by gzip, do not save the original file name and time stamp. [YOCTO #11916] (From OE-Core rev: c32d526a056adb8ed1eb8beb9d495bfd01af2342) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-docutils: update to 0.14Jose Lamego2017-08-161-3/+3
| | | | | | | | | | | | | | python3-docutils recipe must be upgraded to latest stable release. LIC_FILES_CHKSUM changed due to a typo fix from previous version, but license type and information remained the same. This change was tested on qemu with core-image-minimal. (From OE-Core rev: f99247335485e15c820991e3ea20b766364111fc) Signed-off-by: Jose Lamego <jose.a.lamego@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python*-setuptools: update to 36.2.7Jose Lamego2017-08-163-2/+2
| | | | | | | | | | | | Both python-setuptools and python3-setuptools must be updated to latest stable release. These changes were tested on qemu with core-image-minimal (From OE-Core rev: 147d9260eb79edfdf7a91fb8bc3d915f141dc685) Signed-off-by: Jose Lamego <jose.a.lamego@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* run-postinsts: do not reload daemon configurationMax Krummenacher2017-08-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case a systemd service disables itself while init is still in its boot sequence the reloading of the service files can be problematic. In that case: It seems that systemd looses the state of .device units, and some services depend on such units (namely serial consoles such as serial-getty@ttymxc0.service). As a result no getty is spawned on the affected serial tty. After a power-cycle the second boot (which does not disable services) succeeds. The following sequence shows this problem: | Jan 09 16:36:28 apalis-t30 systemctl[162]: Removed /etc/systemd/system/sysinit.target.wants/run-postinsts.service. | Jan 09 16:36:28 apalis-t30 systemd[1]: Reloading. | ... | And then the failing one: | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start timed out. | Feb 22 15:33:15 apalis-t30 systemd[1]: Timed out waiting for device dev-ttyS0.device. | Feb 22 15:33:15 apalis-t30 systemd[1]: Dependency failed for Serial Getty on ttyS0. | Feb 22 15:33:15 apalis-t30 systemd[1]: serial-getty@ttyS0.service: Job serial-getty@ttyS0.service/start failed with result 'dependency'. | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start failed with result 'timeout'. | Feb 22 15:33:15 apalis-t30 systemd[1]: Reached target Login Prompts. (the time has been updated between this two events, but that does not influence the issue) Using --no-reload in the service file avoids the "Reloading." message above and seems to not cause such issues anymore. Reported-by: Stefan Agner <stefan.agner@toradex.com> (From OE-Core rev: 23b359b6e26d0b17037bf955bd15a16a3fd9ab8f) Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> (cherry picked from commit 4a425d05bac5dcba023b67aa3d726f7e7869404f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* opkg-configure: do not reload daemon configurationMax Krummenacher2017-08-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case a systemd service disables itself while init is still in its boot sequence the reloading of the service files can be problematic. In that case: It seems that systemd looses the state of .device units, and some services depend on such units (namely serial consoles such as serial-getty@ttymxc0.service). As a result no getty is spawned on the affected serial tty. After a power-cycle the second boot (which does not disable services) succeeds. The following sequence shows this problem: | Jan 09 16:36:28 apalis-t30 systemctl[162]: Removed /etc/systemd/system/sysinit.target.wants/run-postinsts.service. | Jan 09 16:36:28 apalis-t30 systemd[1]: Reloading. | ... | And then the failing one: | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start timed out. | Feb 22 15:33:15 apalis-t30 systemd[1]: Timed out waiting for device dev-ttyS0.device. | Feb 22 15:33:15 apalis-t30 systemd[1]: Dependency failed for Serial Getty on ttyS0. | Feb 22 15:33:15 apalis-t30 systemd[1]: serial-getty@ttyS0.service: Job serial-getty@ttyS0.service/start failed with result 'dependency'. | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start failed with result 'timeout'. | Feb 22 15:33:15 apalis-t30 systemd[1]: Reached target Login Prompts. (the time has been updated between this two events, but that does not influence the issue) Using --no-reload in the service file avoids the "Reloading." message above and seems to not cause such issues anymore. Reported-by: Stefan Agner <stefan.agner@toradex.com> (From OE-Core rev: 059bc9b164d239f0ba319f8e6a54b5edf7761b22) Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> (cherry picked from commit 16b7b455ee40fd1be5bb9aacf24b106df0d9325e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dpkg-configure: do not reload daemon configurationMax Krummenacher2017-08-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In case a systemd service disables itself while init is still in its boot sequence the reloading of the service files can be problematic. In that case: It seems that systemd looses the state of .device units, and some services depend on such units (namely serial consoles such as serial-getty@ttymxc0.service). As a result no getty is spawned on the affected serial tty. After a power-cycle the second boot (which does not disable services) succeeds. The following sequence shows this problem: | Jan 09 16:36:28 apalis-t30 systemctl[162]: Removed /etc/systemd/system/sysinit.target.wants/run-postinsts.service. | Jan 09 16:36:28 apalis-t30 systemd[1]: Reloading. | ... | And then the failing one: | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start timed out. | Feb 22 15:33:15 apalis-t30 systemd[1]: Timed out waiting for device dev-ttyS0.device. | Feb 22 15:33:15 apalis-t30 systemd[1]: Dependency failed for Serial Getty on ttyS0. | Feb 22 15:33:15 apalis-t30 systemd[1]: serial-getty@ttyS0.service: Job serial-getty@ttyS0.service/start failed with result 'dependency'. | Feb 22 15:33:15 apalis-t30 systemd[1]: dev-ttyS0.device: Job dev-ttyS0.device/start failed with result 'timeout'. | Feb 22 15:33:15 apalis-t30 systemd[1]: Reached target Login Prompts. (the time has been updated between this two events, but that does not influence the issue) Using --no-reload in the service file avoids the "Reloading." message above and seems to not cause such issues anymore. Reported-by: Stefan Agner <stefan.agner@toradex.com> (From OE-Core rev: e735c176361fca43420565dcb8900bbff2f3664e) Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com> (cherry picked from commit 94fabe4b03e899d8876027ee2ced649737a9e522) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* selftest: fix distrodata.py to use per-recipe UPSTREAM_VERSION_UNKNOWN settingAlexander Kanavin2017-08-168-1/+8
| | | | | | | | | | | ... instead of a global exception list which was problematic. [YOCTO #11896] (From OE-Core rev: 89dfede4ca795ba085f1ee7290c6dede573c11db) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pax-utils: check upstream version from debian serversAlexander Kanavin2017-08-161-0/+2
| | | | | | | | | Gentoo server can be very slow to list the tarball directory. (From OE-Core rev: 4f6059a6582d5fdd7260b816301e939d1e3f3ddb) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: Upgrade to 2.29Khem Raj2017-08-1628-1093/+470
| | | | | | | (From OE-Core rev: 3bf990eb275f63190a2cf7253527d6d49fd93f1a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python-numpy: Upgrade to 1.13.1Khem Raj2017-08-133-28/+25
| | | | | | | | | | | | | | Update LICENSE to BSD-3-Clause as per https://github.com/numpy/numpy/blob/master/LICENSE.txt LIC_FILES_CHKSUM changed due to copyright year change see https://github.com/numpy/numpy/commit/b2ff4f13197dd58508d3d025a9034519974750bd (From OE-Core rev: a703bb6159dd69020fb40db7a6a0811f45869972) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: apic: fallthrough to PICHe Zhe2017-08-132-0/+47
| | | | | | | | | | | | Backport a commit from qemu upstream to fix a protection fault https://lists.gnu.org/archive/html/qemu-devel/2013-04/msg00878.html (From OE-Core rev: 88a4a872a7f22be52faa965bc05c57d8466e0eed) 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>
* gcc7: fix potential segmentation faultJuro Bystricky2017-08-132-0/+50
| | | | | | | | | | | | | | | | | | | | Under some rare circumstances we may end up with GCC segmentation fault. This was observed with versions of sysmacros.h, which contain macros with embedded warning messages : When trying to actually display the warning, we may end up with a segmentation fault instead. The reason is the actual warning message gets parsed (the text is unquoted) and words in the message such as "not", "and" etc. are interpreted as operators CPP_NOT, CPP_AND. When the time comes to display the warning, the code uses wrong structure to access the "name" corresponding to the operators. [YOCTO #11738] (From OE-Core rev: 6f81fe4f3a1177c0049b26a070e43546bc6fe974) Signed-off-by: Juro Bystricky <juro.bystricky@intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: update to 4.12Alexander Kanavin2017-08-132-2/+34
| | | | | | | | | | | Add a patch to force a native build for a helper binary (which is not installed or used outside of the build process). (From OE-Core rev: 35e3ed68fd25941e3d76e5a063299b1d1cee0e70) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gptfdisk: update to 1.0.3Alexander Kanavin2017-08-131-2/+2
| | | | | | | | (From OE-Core rev: 9f635de4fc6ce9d32d2298679d6afce745ca5d80) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libdnf: update to 0.9.3Alexander Kanavin2017-08-131-1/+1
| | | | | | | | (From OE-Core rev: aea24b3c6934921852c7de1da15ff326da992d08) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* dnf: update to 2.6.3Alexander Kanavin2017-08-133-51/+2
| | | | | | | | (From OE-Core rev: 685d7ec1114fa2ec4aa44f7e29d1e159f7899d4d) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python2/python3: fix multiprocessing.BoundedSemaphore not work on ↵Hongxu Jia2017-08-134-0/+166
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | qemux86/qemuarm In upstream, the following commit: https://github.com/python/cpython/commit/e711cafab13efc9c1fe6c5cd75826401445eb585 ... commit e711cafab13efc9c1fe6c5cd75826401445eb585 Author: Benjamin Peterson <benjamin@python.org> Date: Wed Jun 11 16:44:04 2008 +0000 Merged revisions 64104,64117 via svnmerge from svn+ssh://pythondev@svn.python.org/python/trunk ... (see diff in setup.py) It assigned libraries for multiprocessing module according the host_platform, but not pass it to Extension. In glibc, the following commit caused two definition of sem_getvalue are different. https://sourceware.org/git/?p=glibc.git;a=commit;h=042e1521c794a945edc43b5bfa7e69ad70420524 (see diff in nptl/sem_getvalue.c for detail) `__new_sem_getvalue' is the latest sem_getvalue@@GLIBC_2.1 and `__old_sem_getvalue' is to compat the old version sem_getvalue@GLIBC_2.0. If not explicitly link to library pthread (-lpthread), it will load glibc's sem_getvalue randomly at runtime. Such as build python on linux x86_64 host and run the python on linux x86_32 target. If not link library pthread, it caused multiprocessing bounded semaphore could not work correctly. ... >>> import multiprocessing >>> pool_sema = multiprocessing.BoundedSemaphore(value=1) >>> pool_sema.acquire() True >>> pool_sema.release() Traceback (most recent call last): File "<stdin>", line 1, in <module> ValueError: semaphore or lock released too many times ... And the semaphore issue also caused multiprocessing.Queue().put() hung. (From OE-Core rev: ca1542cdf6b6437a2f3dcdb33ac5216bf841c04a) 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>
* llvm: Keep llvm-native dependency with clang toolchainKhem Raj2017-08-131-2/+0
| | | | | | | | | | | This was needed when we were conflicting with clang-native but this is solved via append PN to binaries of llvm-native (From OE-Core rev: 82ea78bd2f03b6ba4d720595d3a3fbd96e0232f9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: enable on mips soft-floatAndré Draszik2017-08-131-2/+0
| | | | | | | | | | | | | | | Valgrind support for mips soft-float hosts has been fixed in the 3.12 [1] and 3.13 [2] releases, so let's start building it on those, too. [1] https://sourceware.org/git/?p=valgrind.git;a=commit;h=8f0070d31daea6f0ed18f8fe69498a67530bfcbb [2] https://sourceware.org/git/?p=valgrind.git;a=commit;h=3172936d63da4b6257099bc05aee5793978269cb (From OE-Core rev: 82dbad6aa1390668aa86d28c8a3125b68d6072fa) Signed-off-by: André Draszik <adraszik@tycoint.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: Raise SkipRecipe exception for unsupported architecturesNathan Rossi2017-08-091-2/+1
| | | | | | | | | | | | | | | | | | | | | | When parsing this recipe on an unsupported or non-mappable architecture an error is generated despite no dependencies on the recipe. E.g. ERROR: .../llvm_git.bb: cannot map 'microblazeel' to a supported llvm architecture Instead of generating an error which might confuse users, raise a SkipRecipe exception similar to other arch-style mapping functions (e.g. go_map_arch). This avoids showing the error during parse, and prevents the use of the recipe on unsupported targets. Resulting in an error like so when trying to build llvm: ERROR: Nothing PROVIDES 'llvm' llvm was skipped: Cannot map 'microblazeel' to a supported LLVM architecture (From OE-Core rev: d796abac982f368aa088a291560b565cc47a2c27) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mesa, llvm: Use native version of llvm-configKhem Raj2017-08-091-7/+9
| | | | | | | | | | | | We have a variable YOCTO_ALTERNATE_EXE_PATH to point to target sysroot, utilize this in mesa to use native version of llvm-config to report values from target sysroot. (From OE-Core rev: 1c4444f7b2f5cbcaaf6f9d21d7b4f86555ed746a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* chrpath: use https for SRC_URIRoss Burton2017-08-091-1/+1
| | | | | | | | | | Alioth always redirects, so we might as well save time by looking in the right place. (From OE-Core rev: e681e25fb8fb97a8592df69180d2fd85d136352c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* automake: Add missing libtool tag for cppasm languageKhem Raj2017-08-092-0/+28
| | | | | | | | | | | | | | | This is highlighted when CC is passing flags like -fPIE which are stripped by libtool when building shared libs and replaced with -fPIC, this actually results in CC not matching the CC computed from cmdline created for compiling and as a result libtool heuristic to compute tags auotmatically fails. (From OE-Core rev: 519c34adeb0735f6ff606addd00a7bbe19f4b15c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-pycairo: Pass -fPIC via CFLAGSKhem Raj2017-08-091-0/+2
| | | | | | | | | | | | | | Fixes | /mnt/a/oe/build/tmp/work/corei7-64-bec-linux/python3-pycairo/1.10.0-r2/recipe-sysroot-native/usr/bin/x86_64-bec-linu x/x86_64-bec-linux-ld: src/cairomodule.c.1.o: relocation R_X86_64_PC32 against symbol `CairoError' can not be used whe n making a shared object; recompile with -fPIC (From OE-Core rev: 058b155a66c5f81573379d258250323c72901ff7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Remove -fPIE -pie from SECURITY_PIE_CFLAGSKhem Raj2017-08-091-0/+1
| | | | | | | | | | | | | | | External compilers will explicitly pass -fPIE -pie flags unlike internal toolchain which does not use them, so the build fails with external toolchains because, its passing these flags to linker when building with -r option and fails to link | /mnt/a/oe/build/tmp/work/corei7-64-bec-linux/go/1.8.3-r0/recipe-sysroot-native/usr/bin/x86_64-bec-linux/x86_64-bec-linux-ld: -r and -pie may not be used together (From OE-Core rev: bb89849b5edb05a953586d190826a67ba87c1c5a) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ossp-uuid, libffi, libgcrypt: Pass --tag=CC option to libtoolKhem Raj2017-08-092-0/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | libtool tries to guess the --tag value based on CC/CXX environment variables and the compile commandline generated by makefiles. This heuristics however fails when we construct CC variables in OE and add security flags to it, especially -fPIE -pie which are added by external compilers e.g. clang particularly. It fails because libtool removed PIE flags from compiler cmdline intelligently if it figures out that its building a library, which means that the CC variable passed from cmdline does not match with the compiler cmdline constructed by libtool and we end up with errors like | arm-bec-linux-musleabi-libtool: compile: unable to infer tagged configuration | arm-bec-linux-musleabi-libtool: error: specify a tag with '--tag' This works with internal gcc toolchain because we configure gcc for PIE when hardening is selected and dont pass -fPIE -pie options explicitly but this is not an option for clang, and some external gcc toolchains using older gcc This patch adds the --tag option to help libtool set correct tags in packages where it cant get it right via its heuristics (From OE-Core rev: 0505075ae8d339ba097aebb82b4d0ae62f87c0a9) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* diffstat: exclude aclocalRoss Burton2017-08-091-7/+2
| | | | | | | | | | Instead of moving aclocal.m4 to acinclude.m4 in a custom do_configure, simply tell autoreconf not to run aclocal. (From OE-Core rev: 5cc53ea9347035f96a721ab057a338eded5c5c67) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* diffstat: use HTTP mirror for SRC_URIRoss Burton2017-08-091-1/+1
| | | | | | | | | | The Invisible Mirror FTP service is currently down, and FTP is horrible, so switch to the HTTP mirror. (From OE-Core rev: f31461f8ea11e82dbe14454a1149d9ec2120404d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python: don't include -tests with modulesMark Asselstine2017-08-032-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Although 'test' is listed in the python module list (https://docs.python.org/3/py-modindex.html) it is meant only to be used 'internally' by folks developing python itself. Per the documentation: Note The test package is meant for internal use by Python only. It is documented for the benefit of the core developers of Python. Any use of this package outside of Python’s standard library is discouraged as code mentioned here can change or be removed without notice between releases of Python. Per the above it is best not to include this module to discourage folks who might not head the above warnings. Additionally this module is one of the largest py modules going, by dropping this unneeded module from the 'modules' package we can reduce overall image size, something which is important for many embedded deployments. The generator scripts as well as the manifests have thus been modified accordingly, providing a generic mechanism to exclude modules from the 'all modules' package. (From OE-Core rev: a5bb13a5d7d7a668ca61da6b17884e3b05b95355) Signed-off-by: Mark Asselstine <mark.asselstine@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf-archive: GPLv3 + autoconf exceptionPatrick Ohly2017-08-031-2/+3
| | | | | | | | | | | | | The COPYING file specifies pure GPLv3, not GPLv2 & GPLv3, with the autoconf exception in COPYING.EXCEPTION. OE-core currently has GPL-3.0-with-GCC-exception for this in meta/conf/licenses.conf, so this is used here despite the deprecation note for that license identifier in https://spdx.org/licenses/GPL-3.0-with-autoconf-exception. (From OE-Core rev: 5849391a1854743af26503db603ad578d8d19e25) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* llvm: Add recipe for 5.0Khem Raj2017-07-313-0/+314
| | | | | | | | | | | | | Based on recipe from meta-oe and clang recipe from meta-clang Needed by mesa Fixes [YOCTO #11529] (From OE-Core rev: 8724ef9c53e7804ead9ba0f019369b0e4daada63) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ninja: Add recipeKhem Raj2017-07-311-0/+29
| | | | | | | | | llvm is using it, therefore move it from meta-oe (From OE-Core rev: fc3aef67a95a90e9a485c6b0e93db8cdeab5d3ab) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rm_work: Improve handling for addto_recipe_sysrootRichard Purdie2017-07-311-1/+0
| | | | | | | | | | | Rather than requiring each user to handle this individually, handle addto_recipe_sysroot in the core class. As well as preserving the sysroot directory, this also ensures the stamp is preserved rather than rerunning the task every time as currently happens. (From OE-Core rev: bf8b9858d9ccce27173d13938a83d249294cc473) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf: fix typo in SUMMARYDenys Dmytriyenko2017-07-301-1/+1
| | | | | | | (From OE-Core rev: fb6500144f2244815be3f81908ee3baad373e348) Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf-archive: simplify and fix recipePatrick Ohly2017-07-302-20/+7
| | | | | | | | | | | | | | | | | | | The COPYING file specifies pure GPLv3, not GPLv2 & GPLv3. There is also the COPYING.EXCEPTION file with the autotools exception, which gets ignored here in the recipe to keep it simpler. All of the explicit dependencies seem unnecessary, and RDEPENDS_${PN} doesn't do anything for native recipes either, so all of that gets removed. It also built fine without the m4 and parallel build workarounds. There's no need to have a separate .inc file. (From OE-Core rev: 5002004b891895654cbad53555ee46e2ed188630) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf-archive: move from meta-oe to OE-corePatrick Ohly2017-07-302-0/+26
| | | | | | | | | | | | | | | | | | | | | Having common macros in OE-core that are needed by autotools based projects makes sense. For example, tpm2.0-tools in meta-measured depended on meta-oe only because of autoconf-archive. This is a verbatim copy of the autoconf-archive recipe in meta-openembedded rev 1cbd1bc1, with just one change: the patch which disabled the installation of ax_code_coverage.m4 and ax_check_enable_debug.m4 and the dependency on gnome-common were removed. So now autoconf-archive in OE-core provides them. gnome-common in meta-oe will be changed to not install them and instead depend on autoconf-archive. (From OE-Core rev: 40711432b82fc6efb9e40748532ed68a64fbe628) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vala: upgrade to 0.36.4Alexander Kanavin2017-07-271-2/+2
| | | | | | | (From OE-Core rev: 03d0beec5b5e6cadbda398a28c754811a71e529e) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: upgrade to 4.11.1Alexander Kanavin2017-07-271-1/+1
| | | | | | | (From OE-Core rev: c1152321e3bcf7a61103d77759da17575155225c) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-config: update SRC_URI to new savannah.gnu.org hostnameAndre McCurdy2017-07-271-1/+1
| | | | | | | | | http://sv.gnu.org/ now redirects to http://savannah.gnu.org/ (From OE-Core rev: cf21f45fc7fa7a70df48e9eb6bdf38d0aa902f9b) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: centralize definition of COMPATIBLE_HOSTJoe Slater2017-07-272-10/+0
| | | | | | | | | Put it in goarch.bbclass which all go related recipes inherit. (From OE-Core rev: 9e899bbc081cb932c1492f6d6802b908d70ef42f) Signed-off-by: Joe Slater <jslater@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: allow to enable RPM file signingLans Zhang2017-07-271-0/+3
| | | | | | | | | | | | RPM file signing is enabled with --with-imaevm during configuration. If enabled, the RPM signing tool rpmsign will call libimaevm.so provided by the recipe ima-evm-utils. (From OE-Core rev: 9d7797e4374c111f0dff523fd49354bcc33dc2af) Signed-off-by: Lans Zhang <jia.zhang@windriver.com> Signed-off-by: Jia Zhang <lans.zhang2008@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: fix upstream version checkAlexander Kanavin2017-07-251-0/+1
| | | | | | | | (From OE-Core rev: f4e86314dac536755b2489a5b442b0f36909cae5) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: use HTTP instead of FTP to fetchRoss Burton2017-07-251-1/+1
| | | | | | | | | FTP is inferiour to HTTP is all respects, so use the HTTP URL for the tarball. (From OE-Core rev: 6a9e38be6e9dcbeff033944f9a3a18e3838af10d) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python.inc: set CVE_PRODUCT to pythonMikko Rapeli2017-07-241-0/+2
| | | | | | | | | | | | | All python versions are just python in NVD like this CVE for python 3.4.4: https://nvd.nist.gov/vuln/detail/CVE-2016-5699 (From OE-Core rev: 848e1be494e8ea10c729f95f02acb366e1843d75) Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc-common.inc: set CVE_PRODUCT to gccMikko Rapeli2017-07-241-0/+2
| | | | | | | | | | | | All recipes which include this are using gcc as product name in NVD like https://nvd.nist.gov/vuln/detail/CVE-2015-5276 (From OE-Core rev: bd6f1430334412588c143d8029be39fe814672cd) Signed-off-by: Mikko Rapeli <mikko.rapeli@bmw.de> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm/dnf: fix Upstream-Status to reflect upstream submission statusAlexander Kanavin2017-07-2413-13/+13
| | | | | | | | (From OE-Core rev: 1ed4b8438087fe6d61203ffbe9737ac382e0d6eb) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python*-setuptools: upgrade to 36.2.0Jose Lamego2017-07-243-4/+4
| | | | | | | | | | | | | | | | Both python-setuptools and python3-setuptools need to be upgraded to latest upstream version. license checksum is now targeted to be performed over the actual license text at license file. These changes were tested using qemux86 with core-image-minimal. (From OE-Core rev: 6ad635a33b5a49fa51165b6ac7606b27438f5d96) Signed-off-by: Jose Lamego <jose.a.lamego@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mkelfimage: Fix build on x86_64 with hardeningKhem Raj2017-07-241-0/+1
| | | | | | | | | | | | | | | | | | | | We get linking errors on some hosts like | ld -static --warn-multiple-gp --warn-common -T linux-i386/convert.lds -o objdir/linux-i386/convert ob jdir/linux-i386/head.o objdir/linux-i386/convert_params.o | objdir/linux-i386/convert_params.o: In function `printf': | convert_params.c:(.text+0x1fd): undefined reference to `__stack_chk_fail_local' This is because the build system is defaulting to host linker when building 32bit binaries and it may not have same defaults as OE toolchain and issue gets highlighted. fix it by using cross linker for 32bit links when building on x86_64 (From OE-Core rev: 470c8a0fb5f51a626a194c8fd3aabd448b50ebfa) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patchelf: fix segfault for binaries linked by goldEd Bartosh2017-07-242-0/+39
| | | | | | | | | | | | | | | | | | | | | Due to a bug in calculating adresses of modified program headers patchelf breaks executables linked by Gold linker causing them to segfault, e.g. $ tmp/sysroots-components/x86_64/m4-native/usr/bin/m4 --help Segmentation fault This is reproducible only in some cases and only for executables of ET_DYN type produced by Gold or by ld linked with pie. This should be solved by fix-adjusting-startPage.patch that fixes calculation logic. [YOCTO #11785] (From OE-Core rev: 4e4c96db4b1d2356b5d071cee6746a96eca20439) Signed-off-by: Ed Bartosh <ed.bartosh@linux.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-17 22:39:51 +0000