summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
Commit message (Collapse)AuthorAgeFilesLines
* valgrind: Fix build on musl after drd fixesRichard Purdie2020-10-262-0/+32
| | | | | | (From OE-Core rev: 6a74caa115298e594ae22a9de91b132db62e4b5d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: drd: fix pthread intercept test failuresStacy Gaikovaia2020-10-262-0/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | After glibc uprev 2.31 -> 2.32, the following drd ptests fail with the error "condition variable has not been initialized". drd/tests/annotate_hb_err drd/tests/annotate_sem drd/tests/annotate_rwlock drd/tests/annotate_order_2 drd/tests/annotate_smart_pointer drd/tests/annotate_spinlock drd/tests/monitor_example drd/tests/pth_cond_race drd/tests/pth_inconsistent_cond_wait In glibc 2.32, the POSIX thread functions are in both libc and libpthread, causing valgrind to misinterpert test behaviour. This patch tells valgrind to intercept both the libc and the libpthread functions, resolving these ptest failures. Here are the latest test results on qemux86-64: === Test Summary === TOTAL: 728 PASSED: 688 FAILED: 1 SKIPPED: 39 The failed test is in helgrind: FAIL: helgrind/tests/pth_destroy_cond Patch can be removed once we uprev valgrind. See valgrind commit 15330adf7c2471fbaa6a0818db07078d81dbff97. (From OE-Core rev: e8f265e957e187b4f84f566aaeec8f514e3044d6) Signed-off-by: Stacy Gaikovaia <Stacy.Gaikovaia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* tcl: adapt to potential pseudo changesMingli Yu2020-10-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It failed as below when rerun do_install for tcl: $ bitbake tcl $ bitbake tcl -f -cinstall [snip] | NOTE: make -j 72 DESTDIR=/build/tmp/work/core2-64-wrs-linux/tcl/8.6.10-r0/image install | abort()ing pseudo client by server request. See https://wiki.yoctoproject.org/wiki/Pseudo_Abort for more details on this. | /build/tmp/work/core2-64-wrs-linux/tcl/8.6.10-r0/temp/run.do_install.3490694: line 184: 3499214 Aborted (core dumped) make -j 72 "$@" By default the S is ${WORKDIR}/${BPN}-${PV}, but after unpack, the tcl source [1] unpacked to ${WORKDIR}/${BPN}${PV} and all the files under ${WORKDIR}/${BPN}${PV} are acutally the source files. But the the main Makefile.in is under ${WORKDIR}/${BPN}${PV}/unix for tcl, so there is below logic in tcl recipe: S = "${WORKDIR}/${BPN}${PV}/unix" To adapt the potential pseudo changes, there is a general logic to exclude ${S} from pseudo database in base.bbclass in [2]. That's to say, just the dir ${WORKDIR}/${BPN}${PV}/unix is excluded from the pseudo database. But it's not enough for tcl, we need to exclude the actual source dir ${WORKDIR}/${BPN}${PV} from pseudo database specifically to fix the above do_install failure. [1] https://downloads.sourceforge.net/tcl/tcl8.6.0-src.tar.gz [2] https://git.openembedded.org/openembedded-core/tree/meta/classes/base.bbclass#n396 (From OE-Core rev: 0d835f8069a336fd6bab1058d4e605a81c844212) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: change TLBs number to 64 in 34Kf mips cpu modelVictor Kamensky2020-10-202-0/+60
| | | | | | | | | | | | Replace OE private qemu patch with one that got upstreamed and solves the same problem: increase qemumips CI performance by increasing number of TLBs in CPU model and reduce need to run software TLB refill code. (From OE-Core rev: a99dace7463d310688f4098a51316dc0743651e2) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "qemu: add 34Kf-64tlb fictitious cpu type"Victor Kamensky2020-10-202-119/+0
| | | | | | | | | | | This reverts commit 4470a04943352224955f17e004962f0f9e1c9b0c. Will be replaced with upstreamed solution instead, that just bumped number of TLBs to 64 in original 34Kf CPU model. (From OE-Core rev: 894f1d58d93073d290f35d1090b03717bc7b4dc0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: fix upstream version checkAlexander Kanavin2020-10-201-0/+1
| | | | | | | (From OE-Core rev: c8a6512b36e12f48d8713c5c3b48d83a431c8191) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* mtd-utils: don't use trailing slash in SMartin Jansa2020-10-101-1/+1
| | | | | | | (From OE-Core rev: c77651549dd382007c60767076a1a1c72e282bca) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Upgrade to include mkostemp64 wrapperRichard Purdie2020-10-091-1/+1
| | | | | | | | | | | Newer systems are using this currently unwrapped glibc function, add it. [YOCTO #14080] (From OE-Core rev: cba4f51f0166e2c20e854ee0344be0c58769eaca) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Update to account for patches merged on branchRichard Purdie2020-10-099-735/+1
| | | | | | (From OE-Core rev: ea22fb3aa1c5dd3edcd1d8b415a0843a9ee4677c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: add 34Kf-64tlb fictitious cpu typeVictor Kamensky2020-10-082-0/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Yocto Project PR 13992 it was reported that qemumips in autobuilder runs almost twice slower then qemumips64 and some times hit time out. Upon investigations of qemu-system with perf, gdb, and SystemTap and comparing qemumips and qemumips64 machines behavior it was noticed that qemu soft mmu code behaves quite different and in case if qemumips tlbwr instruction called 16 times more oftern. It happens that in qemumips64 case qemu runs with cpu type that contains 64 TLB, but in case of qemumips qemu runs with cpu type that contains only 16 TLBs. The idea of proposed qemu patch is to introduce fictitious 34Kf-64tlb cpu type that defined exactly as 34Kf but has 64 TLBs, instead of original 16 TLBs. Testing of core-image-full-cmdline:do_testimage with 34Kf-64tlb shows 40% or so test execution real time improvement. Note for future porters of the patch: easiest way to update the patch and be in sync with 34Kf definition is to copy 34Kf machine definition and apply the following changes to it (just change 15 to 63 of CP0C1_MMU bits value) [kamensky@coreos-lnx2 qemu]$ diff ~/34Kf.c ~/34Kf-64tlb.c 2c2 < .name = "34Kf", > .name = "34Kf-64tlb", 6c6 < .CP0_Config1 = MIPS_CONFIG1 | (1 << CP0C1_FP) | (15 << CP0C1_MMU) | > .CP0_Config1 = MIPS_CONFIG1 | (1 << CP0C1_FP) | (63 << CP0C1_MMU) | Fixes https://bugzilla.yoctoproject.org/show_bug.cgi?id=13992 Upstream Status: Inappropriate (From OE-Core rev: 4470a04943352224955f17e004962f0f9e1c9b0c) Signed-off-by: Victor Kamensky <kamensky@cisco.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* strace: Fix value of IPPROTO_MAXKhem Raj2020-10-082-0/+71
| | | | | | | | | | | | | This should also fix build with musl ../strace-5.8/xlat/inet_protocols.h:239:1: error: static assertion failed: "IPPROTO_MAX != 256" 239 | static_assert((IPPROTO_MAX) == (256), "IPPROTO_MAX != 256"); | ^~~~~~~~~~~~~ (From OE-Core rev: 8b0438b5d4850aaca0f725f9ad5d040b90b1347b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Fix statx function usageRichard Purdie2020-10-082-0/+57
| | | | | | | | | | | There is magic in the posts where specific variable names have specific magic. For that magic to work, "path" needs to be used not "pathname" as is currently there. Fix this, which fixes path issues on systems using statx (Ubuntu 20.04 in particular). (From OE-Core rev: f9ae80aee98a7bb59c83ac9ebf9d317302507cec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Add pathfix patchRichard Purdie2020-10-072-0/+26
| | | | | | | | | Add a path to fix up handling of dirfd being passed as a full file and with path="". (From OE-Core rev: 3006bbe7768e4efe33d3d2d3f5786a561ecbe96f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Add may unlink patchRichard Purdie2020-10-072-0/+38
| | | | | | | | | Mark files which are unlinked (nlink == 0) but open with fd's as "may-unlink" to avoid problematic database entries. (From OE-Core rev: e1e481f3608c05ab14c61bf45cd0837d7287b6a5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Fix xattr segfaultRichard Purdie2020-10-072-0/+41
| | | | | | | | | Fix a NULL pointer dereference exposed by the path ignore code in xattr handling. (From OE-Core rev: 929a27bf6cbca94d1141d2094ae0c915d93bd3f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* psuedo: Add tracking of linked files for fdsRichard Purdie2020-10-072-0/+156
| | | | | | | | | | Where files are link()'d and one is unlink()'d, pseudo's fd mappings can become confused. Add a patch to try and improve this for the common usecases we see. (From OE-Core rev: 9ce621fa2099608ca0ccbb8420b31d71cdd7b00e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Abort on mismatch patchRichard Purdie2020-10-072-0/+65
| | | | | | | | | | | Rather than doing what turns out to be a rather dangerous "fixup" if we see a file with a different path but the same inode as another file we've previously seen, throw and abort. Direct the user to a wiki page where we can maintain information about what this error means. (From OE-Core rev: 2db491d97da08d44ebd257f98489550a82a7935c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Add support for ignoring paths from the pseudo DBRichard Purdie2020-10-072-0/+299
| | | | | | | | | | | | Add PSEUDO_IGNORE_PATHS, a comma separated list of path prefixes, where any files underneath are not handled by pseudo. This allows files to be left out of the pseudo datanase where we know we don't need the fake root emulation. This is particularly useful if we know these files can be deleted outside of pseudo context. (From OE-Core rev: 8defb687a2c0ffac232c4d0d63a590871c453a2e) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: Ignore mismatched inodes from the dbRichard Purdie2020-10-072-0/+52
| | | | | | | | | | | | | | | | | | | | Currently, where pseudo finds a database entry for an inode but the path doesn't match, it reuses that database entry metadata. This is causing real world "corruption" of file attributes. See [YOCTO #14057] for an example of this. This can happen when files are deleted outside of pseudo context and the inode is reused by a new file which pseduo then "sees". Its possible the opposite could happen, it needs to reuse attributes but this change would prevent it. As far as I can tell, we don't want pseuo to reuse these attributes though so this code should be safer and avoid bugs like the above. (From OE-Core rev: 1c13149b81e03a1ac48b27a208a139d5493c3ce7) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libtools-cross/shadow-sysroot: Use nopackages inheritRichard Purdie2020-10-061-0/+2
| | | | | | | | | When testing pseudo changes I realised these recipes have packaging tasks but don't generate packages. Drop the packages tasks for cleanliness. (From OE-Core rev: ef9c11797b5d626bdb40b4509d8b2b0d461ff9ea) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: add PACKAGECONFIG for the systemd inhibit pluginRoss Burton2020-09-301-6/+9
| | | | | | | | | | | | | | | | | | | | | | | RPM ships a systemd inhibit plugin, that will tell systemd to inhibit a reboot or sleep during a package upgrades. For native RPM this is entirely useless, and for target it's only useful if you're using systemd+logind+rpm. This plugin uses DBus which means it depends on expat -> cmake-native -> libarchive-native curl-native, which is quite a dependency tree to need in early build (required to build packages via rpm-native). It was previously forcibly disabled for native packages but the build dependency on DBus remained. Add a PACKAGECONFIG for the plugin that is only enabled for target builds with systemd and explicitly disabled for native/nativesdk builds, but also keep the explicit disabling of all plugins as the prioreset plugin also behaves badly inside a build. (From OE-Core rev: df758ea66fd2f69d591c1fd36b90969796d50bd0) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Space-comma CleanupsJon Mason2020-09-302-3/+3
| | | | | | | | | | | | | Multiple files have " ," instead of ", " in expressions. This changes them to conform to the way the rest of them are done. Found and corrected via: git ls-files | xargs sed --follow-symlinks -i 's/ ,d/, d/g' (From OE-Core rev: 36c3afd2dd8bded02ea8f255e89a09ebd75c795b) Signed-off-by: Jon Mason <jon.mason@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: disable libarchive useRoss Burton2020-09-301-3/+4
| | | | | | | | | | | libarchive is only needed for the rpm2archive tool, as this is of limited use and libarchive is a non-trivial build dependency make this optional and disabled by default. (From OE-Core rev: 2eaefac2bb0b999e64a445fdadefb639eb7089a0) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta: add/fix invalid Upstream-Status tagsRoss Burton2020-09-232-2/+2
| | | | | | | (From OE-Core rev: 630ce8130598e2bca7231ac28a7cc18b5b942544) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-jinja2: Import from meta-oe/meta-pythonRichard Purdie2020-09-212-0/+48
| | | | | | | | | | | | | | This is used by some of the results handling code and needed as part of buildtools tarball on various autobuilder worker for testing. ptest is disabled for OE-Core, at least for now since it depends on python3-pytest which in turn has may other dependencies. Acked-by: Tim Orling <ticotimo@gmail.com> (From OE-Core rev: 9d30a3b95ef4dce8925f88c8d8d854ed48c5f367) Signed-off-by: Tim Orling <ticotimo@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-markupsafe: Import from meta-oe/meta-pythonRichard Purdie2020-09-212-0/+31
| | | | | | | | | | | | Needed as a dependency of python3-jinja2. ptest is disabled for OE-Core, at least for now since it depends on python3-pytest which in turn has may other dependencies. Acked-by: Tim Orling <ticotimo@gmail.com> (From OE-Core rev: 94a04a42826ee95a27abe52d43b31b0f053260d9) Signed-off-by: Tim Orling <ticotimo@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* valgrind: fix memcheck vgtests remove fullpath-after flagsStacy Gaikovaia2020-09-172-16/+30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously in: f75792b28e valgrind: make a few more ptests pass the vagrind test runner was adjusted to suppress part of a path that only exists when run in the yocto ptest environment. Unfortunately this change includes the valgrind version and when valgrind was last updated, the patch was not changed. Rather than continually updating the patch or even generating the version dynamically, we can simply change the expected output for two tests. The reason the option: --fullpath-after=foo was introduced into the effected valgrind ptests was to deal with builds where ccache is used. Compiling with ccache enabled sometimes causes the source file absolute name to be found in a full path that is not the same as $PWD. See commit c80f32e662dfa2a4f046960a25d5b8b7a8821bea in valgrind for more information about changes to the arguments that test badfree3 and varinfo5 run with. There is also a minor fix to add the missing overloading.pm perl package and put the dependencies in alphabetic order. (From OE-Core rev: 9c82b9302c6ee84864e9a9cc870729395804e794) Signed-off-by: Stacy Gaikovaia <Stacy.Gaikovaia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bison: remove the parallel build patchMingli Yu2020-09-172-70/+0
| | | | | | | | | | | Remove the parallel build patch and related fix for parallel build as the issue have already been fixed in bison 3.7.2 (f7b642cf build: fix incorrect dependencies). (From OE-Core rev: 00c7aacf84d094706ed3378a265189d2d6816cfd) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: override DEBUG_BUILDMingli Yu2020-09-172-5/+4
| | | | | | | | | | | | | | | | | | Override DEBUG_BUILD for qemu as the qemu upstream states it doesn't work without optimization [1] to fix below build failure when debug build enabled. | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:25: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o: in function `fsdev_co_throttle_request': | /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o:/mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: more undefined references to `unknown_lock_type' follow | collect2: error: ld returned 1 exit status [1]: https://lists.nongnu.org/archive/html/qemu-devel/2020-09/msg03873.html (From OE-Core rev: 2d6a15cfb12e72ae3d38f6ecf8c6c2e356e0fda8) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "qemu: always define unknown_lock_type"Richard Purdie2020-09-173-50/+6
| | | | | | | | | | | | This reverts commit e442924d9ac4e202aec571b5d26bb959b5faaadd. This was rejected upstream and its been pointed out qemu doesn't work without optimization. Instead we should just error if the user attempts to build it without optimization. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Update to 1.15.2 minor releaseKhem Raj2020-09-142-4/+4
| | | | | | | | | This is bug fix release on 1.15 stable version (From OE-Core rev: 0783a84a6b0df84be590f59e70cb80506c774f4d) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: always define unknown_lock_typeMingli Yu2020-09-143-6/+50
| | | | | | | | | | | | | | | | | When use gcc 10.1.0 and debug build is enabled, there comes below build failure: | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:25: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o: in function `fsdev_co_throttle_request': | /mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: undefined reference to `unknown_lock_type' | /usr/lib/gcc/x86_64-wrs-linux/10.1.0/../../../../x86_64-wrs-linux/bin/ld.bfd: ../fsdev/qemu-fsdev-throttle.o:/mnt/build/tmp/work/x86_64-linux/qemu-system-native/5.1.0-r0/qemu-5.1.0/fsdev/qemu-fsdev-throttle.c:103: more undefined references to `unknown_lock_type' follow | collect2: error: ld returned 1 exit status So always define unknown_lock_type to fix the above error. (From OE-Core rev: d88e83d49478a2535575df769329d9b1e6579564) Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: fix CVE-2020-14364Ross Burton2020-09-122-3/+93
| | | | | | | | | Backport a patch from upstream to fix CVE-2020-14364. (From OE-Core rev: 1ffd4d94e879b338e190a2c4798a4e0bada9b5a7) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bison: uprev from 3.7.1 to 3.7.2Stacy Gaikovaia2020-09-121-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | a0bc06b7 (tag: v3.7.2) version 3.7.2 5e33dfe5 build: disable syntax-check warning 2a4e9a35 gnulib: update f7b642cf build: fix incorrect dependencies 3da17724 doc: updates 68e3e442 gnulib: update e432619d tests: beware of sed portability issues a1b7fef0 c: always use YYMALLOC/YYFREE 067e35a8 build: beware of POSIX mode 0522047c doc: history of api.prefix 3724b50e CI: intel moved the script for ICC b801b7b6 fix: unterminated \-escape b7aab2db fix: crash when redefining the EOF token 89e42ffb style: fix missing space before paren 6aae4a73 style: fix comments and more debug trace 7d4a4300 style: more uses of const 31d4ec28 bench: fix support for pure parser 0a5bfb4f portability: multiple typedefs 12d0b156 style: revert "avoid warnings with GCC 4.6" cb7dcb01 maint: post-release administrivia CVE: CVE-2020-24980 fixed by b801b7b6 CVE: CVE-2020-24979 fixed by b7aab2db (From OE-Core rev: 00a259ff93beb32b231843304c0f96c235bc4d22) Signed-off-by: Stacy Gaikovaia <Stacy.Gaikovaia@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: whitelist CVE-2016-10642Ross Burton2020-09-081-0/+4
| | | | | | | | | | This CVE is specific to the npm package that can install cmake, so isn't relevant to our cmake recipe. (From OE-Core rev: 8e74ed809ec4c1f61264ecf5be4bc319e5e07766) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: Upgrade to 1.15 major releaseKhem Raj2020-09-0517-145/+29
| | | | | | | | | | | | | | | | | 1.15 is latest major release changelog is [1] and detailed blog is [2] Drop hardcoding ldso patch in favor of setting it using GO_LDSO variable which can be defined in terms of linuxloader defined by OE Setting GOBUILDMODE to pie is no longer needed [1] https://golang.org/doc/go1.15 [2] https://blog.golang.org/go1.15 (From OE-Core rev: aa1bfaff4adc9246a2d65592b3a8061d55829086) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* help2man: rewrite recipeRoss Burton2020-09-051-8/+7
| | | | | | | | | | | | | | | | | | This recipe was originally explicitly minimal because it was needed to bootstrap autotools, but that isn't the case anymore. Instead of being explicitly native, use BBCLASSEXTEND. No need to explicitly depend on autoconf-native automake-native, because the autotools class does that. As this recipe isn't needed in early build anymore there's no need to avoid reconfiguring. (From OE-Core rev: 1e98edf46d0b96da2aea7dabd1d7cf3ce6c5e7bd) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf: consolidate DEPENDSRoss Burton2020-09-051-3/+2
| | | | | | | | | | | Depending on nativesdk- varients in a nativesdk build isn't correct, so just collapse the DEPENDS down and let bitbake do the right thing (which is leaving them as -native). (From OE-Core rev: 4864167ad4ed4c57e49f2aa5e7c58383bddb052b) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* autoconf: consolidate SRC_URIRoss Burton2020-09-052-16/+14
| | | | | | | | | | There's no point splitting SRC_URI between the .inc and the .bb when there's just one recipe and the splitting appeared to be arbitrary. (From OE-Core rev: f627fa2992420c09e57376fbba62d545512c19f2) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nasm: update 2.15.03 -> 2.15.05Alexander Kanavin2020-09-032-24/+22
| | | | | | | | | Use autotools-brokensep as new version needs that. (From OE-Core rev: c9c724ffa36757b56e70bc8d7b880c0c5777b153) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnu-config: update to latest revisionAlexander Kanavin2020-09-031-2/+2
| | | | | | | (From OE-Core rev: e5f7f40ab0816d20e99f086cfa4161800769d098) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ninja: upgrade 1.10.0 -> 1.10.1Alexander Kanavin2020-09-031-1/+1
| | | | | | | (From OE-Core rev: 2a6ea1b4aecb92116b74d6210523582ba51c64c7) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* librepo: upgrade 1.12.0 -> 1.12.1Alexander Kanavin2020-09-031-1/+1
| | | | | | | (From OE-Core rev: 3a2dd853a02d5299b3ef8251b735c1b52c7fc8ba) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* cmake: upgrade 3.18.1 -> 3.18.2Alexander Kanavin2020-09-034-2/+2
| | | | | | | (From OE-Core rev: b8843d8781fc9312a5ff5551fc59b715b7e42b74) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* log4cplus: move meta-oe pkg to coreakuster2020-09-021-0/+19
| | | | | | | | | pkg need for kea (From OE-Core rev: 4916d9dc2f290058c37830d4a68e8678f95d4c9e) Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* elfutils: silence a new QA warningRoss Burton2020-09-021-0/+2
| | | | | | | | | | | | The fix to the gnu-hash-style check (oe-core 70d932f21) causes elfutils-ptest to emit a new warning. This binary is explicitly compiled with a curated minimal set of compiler flags, so to avoid breaking the test simply skip the ldflags check for elfutils-ptest. (From OE-Core rev: 3ebfc4fc4e448f4dbc5a04ccceaee6f0f7780a43) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* patchelf: upgrade 0.11 -> 0.12Richard Purdie2020-09-021-1/+1
| | | | | | (From OE-Core rev: 41694bc38996a6abfd2a4dabf6283434a538a6d3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-device-devel: removeAlexander Kanavin2020-08-281-16/+0
| | | | | | | | | | The purpose and content of the group is not clear; the only consumer (poky distro) is no longer using it. (From OE-Core rev: 910e26321f6d7583ae68dafafffe2040ca9cfa70) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* pseudo: fix renaming to selfJoe Slater2020-08-271-1/+1
| | | | | | | | | | | | | | Pseudo tests for an item being renamed to itself only after information about it has been deleted. Move the test to before we change the database. Note that pseudo does not support renameat2(), but neither does glibc. (From OE-Core rev: 6b3d109f42385ad1cf1f297a6c06ea7eb6509f26) Signed-off-by: Joe Slater <joe.slater@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gcc10: Don't default back to -fcommonJacob Kroon2020-08-261-1/+0
| | | | | | | | | | | | It has been almost 3 months since the upgrade to gcc 10. Switch back to relying on gcc default configuration (-fno-common). This reverts OE-Core commit 951e859b1e8297970278c539e989b8a6d06a9cb3. (From OE-Core rev: 4ee733e1551d3960a23a600eb71a01cf7a51fa06) Signed-off-by: Jacob Kroon <jacob.kroon@gmail.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-15 00:43:20 +0000