summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2020-01-14mips: Enable gnu-hash-stylekraj/mips-gnu-hashKhem Raj
latest glibc 2.31 [1] and binutils [2] has finally added the needed support for gnu hash-style, which brings mips into same fold as other architectures Fix check for MIPS specific section for gnu hash information [1] https://sourceware.org/ml/libc-alpha/2019-06/msg00456.html [2] https://sourceware.org/ml/binutils/2019-07/msg00098.html Signed-off-by: Khem Raj <raj.khem@gmail.com>
2020-01-13bitbake: runqueue: Use a set for the setscene tasks listRichard Purdie
This should give performance improvements to functions using this list of tasks (sets are used for most of the other code for this reason, not sure why this wasn't a set in the first place). (Bitbake rev: f5daef68703481a3c243dfecc7de404e6ebfdbb6) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-13bitbake: knotty: Be consistent when creating/updating progress barsPeter Kjellerstedt
When creating a new progress bar (using BBProgress), a colon was appended to the supplied message. However, when updating the message, no colon was appended. Change this so that the colon is instead part of the widgets that make up the progress bar so that it does not matter when and how the message is updated, it always displays the same. (Bitbake rev: 08f35c04f6e1ce4c4ca5c2bef4cd8a192e12e682) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-13bitbake: knotty: Hide the footer if a process progress bar is shownPeter Kjellerstedt
With the introduction of the hash equivalence server, the progress bar for "Checking sstate mirror object availability" is shown repeatedly while the tasks are being executed. If the footer is not hidden then, it will be moved up one line every time, creating a messy interface. (Bitbake rev: 56b5ec4c2b3e658e73ca6c3a12feeb96df0977fb) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-13gettext: fix typo in Upstream-StatusRoss Burton
(From OE-Core rev: b6d4150f9c74f25a4022a3fa0bd489a8e85deb77) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-13systemd: add missing Upstream-StatusRoss Burton
(From OE-Core rev: 66d4314c12831cfdbe14130db204fa99e3c77f5e) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-13scripts/oe-build-perf-report: Avoid buildstats warningRichard Purdie
When a comparision branch is set we see warnings. If two branches are used, look for buildstats information from both to avoid this kind of warning: INFO: Parsing buildstats from 'refs/notes/buildstats/perf-centos7.yoctoproject.org/master-next/qemux86' WARNING: Buildstats not found for perf-centos7.yoctoproject.org/master/qemux86/56808-g08220028e52992dcba667fc97bf3afe8be1949fb/0 WARNING: Buildstats not found for perf-centos7.yoctoproject.org/master/qemux86/56808-g08220028e52992dcba667fc97bf3afe8be1949fb/1 INFO: Buildstats were missing for some test runs, please run 'git fetch origin refs/notes/buildstats/perf-centos7.yoctoproject.org/master-next/qemux86:refs/notes/buildstats/perf-centos7.yoctoproject.org/master-next/qemux86' and try again (the warning is due to stats being looked for in both branches, choose the other branch and different warnings would be shown) (From OE-Core rev: af58c18fcd0451540dd77ee862956b2b9dee17c4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-13sstate: Improve move into place op and touch fileRichard Purdie
Depending on the kernel and coreutils version, mv operations test for existence of files and can potentially race. It also leads to the file always changing which leads to potential problems if using and NFS share and there are other readers. Using ln instead means we don't overwrite the file if it already exists meaning other readers aren't disrupted and should work more reliably on NFS which is used for sstate on the autobuilder. Since we're not overwriting files, touch the file to show activity as would have been done it it were reused from sstate. (From OE-Core rev: d8e9a22a4e23616ad01627c1e472296b1e26f13c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11toaster.bbclass: Correct pkgdatadir path in toaster_package_dumpdata()Peter Kjellerstedt
In commit 692b2046 (package: Fix race between do_package and do_packagedata), the path used for do_packagedata[sstate-inputdirs] was changed from "${PKGDESTWORK}" to "${WORKDIR}/pkgdata-pdata-input". This commit adapts the path used for pkgdatadir in toaster_package_dumpdata() accordingly to avoid setscene errors like: ERROR: libgcc-9.2.0-r0 do_packagedata_setscene: Error executing a python function in exec_python_func() autogenerated: The stack trace of python calls that resulted in this exception/failure was: File: 'exec_python_func() autogenerated', lineno: 2, function: <module> 0001: *** 0002:toaster_package_dumpdata(d) 0003: File: 'meta/classes/toaster.bbclass', lineno: 130, function: toaster_package_dumpdata 0126: lpkgdata = {} 0127: datadir = os.path.join(pkgdatadir, 'runtime') 0128: 0129: # scan and send data for each generated package *** 0130: for datafile in os.listdir(datadir): 0131: if not datafile.endswith('.packaged'): 0132: lpkgdata = _toaster_load_pkgdatafile(datadir, 0133: # Fire an event containing the pkg data 0134: bb.event.fire(bb.event.MetadataEvent( Exception: FileNotFoundError: [Errno 2] No such file or directory: 'tmp/work/mips32r2el-nf-poky-linux/libgcc/9.2.0-r0/pkgdata/runtime' (From OE-Core rev: 5a0f6f631b86f7107aa72453b6d23f32ba39f713) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11glib-2.0: Fix hardcoded paths in checksumsRichard Purdie
The expansion by this function, recently added by the meson site handling code was causing hardcoded paths to become embedded in the tash hashes. Avoid this (and hence avoid eSDK failures which exposed this). (From OE-Core rev: 83899aad423cd36cea7ab2ea210feae5b3359823) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11meta-extsdk-toolchain: Mark as nostampRichard Purdie
This recipe needs to generate the latest hashes. With unihash we may not rebuild as previous dependencies may be marked as equivalent. eSDK which uses this is nostamp already, mark this task as nostamp also for the same reason. (From OE-Core rev: e8cfc8525c5d903ee876eafd56521f4a7325a6f5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11glib: support target/os/libc-specific Meson cross filesRoss Burton
Build systems have a common problem that some tests can only be done by executing a piece of test code (compared to just compiling or linking test code). In a cross-compilation the execution of this code isn't possible and the Meson solution to this is to allow 'cross properties' to be specified in the cross files. GLib has a number of these, for example determining the direction the stack grows, whether /proc/self/cmdline exists, or the behaviour of snprintf(). Previously we'd passed values for these to the Glib build for target builds, but this misses out nativesdk builds (which are also cross-compiled) and the fact that some of these values are specific to the platform, some are specific to the host OS, and some are specific to the libc implementation. This problem has already been solved for autotools with the siteinfo class, which turns the target platform/OS/libc variables into filenames (such as common common-linux common-glibc). We can look for these in FILESDIR and use them as cross files. Assuming that there are no problems with this appoach it can be moved into meson.bbclass so that all Meson recipes can use it for their cross files. (From OE-Core rev: 5acd9cbc9d5c6355010775250fb25f043441c5cd) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11weston-init: Let weston run without pam on distros without pamKhem Raj
When pam is not part of distro, user specific XDG_* environment variables are not available since PAMName=login is in-effective and as a result weston can not start because it direly needs XDG_RUNTIME_DIR defined, therefore launching weston directly in systemd service will not work, therefore call the helper script weston-start, which is also used with sysvinit extend enabling fbdev backend fallback to all qemu machines Reported-by: Marek Vasut <marex@denx.de> (From OE-Core rev: ae66cf5e03f04361aad2bd8784fb7d42e0f0bb08) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working mktime()André Draszik
This coreutils (gnulib) test tests for various bugs that only exist in ancient versions. It defaults to assuming buggy behaviour with its own implementation when cross-compiling. musl and recent glibc (2.29) are not affected. (From OE-Core rev: 65d38cc1ce5a106c4c2e5068b8440eb6e5a2b33e) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: strtod() works in glibc / muslAndré Draszik
autoconf has a test for strtod(), which assumes non-working when cross-compiling, but it does work in both musl and recent glibc. coreutils (gnulib) does some additional tests on top of that, but assumes working glibc when >= 2.8 when cross compiling. It doesn't know about musl where the additional tests also work, though. (From OE-Core rev: c8429f707d9ac785f295492470ec8b9ff56c043b) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: set nanosleep() behaviour for glibc / muslAndré Draszik
As per coreutils' (gnulib's) autotools test, nanosleep() misbehaves on glibc (2.29), and works fine on musl. During cross-compile, recent coreutils assume brokenness when compiling for linux, which pessimises musl. Set the correct result for musl, and for coherency reasons, also specify the result for glibc. (From OE-Core rev: 4522648758dc59f5ece736a0c1c0e95dcc7dafd1) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: on linux, link(2) doesn't follow symlinksAndré Draszik
(but gnulib / coreutils assumes yes when cross-compiling) (From OE-Core rev: e1a20bed0d1c6b5fc64c9200fcd8ce2496ce3e08) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: on linux, pipes are fifos with max link count of 1André Draszik
(From OE-Core rev: 13aa567ac1c2c5232378bb9de0bb4ccf04f8c2ac) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working utimes()André Draszik
This coreutils / gnulib autoconf test is for a broken glibc implementation of utimes from 2003-07-12 to 2003-09-17. (From OE-Core rev: a60ca6048cc3a4fef862b128a842c70ac0cd2253) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: linux supports NULL in utime()André Draszik
to set the file to the current time (From OE-Core rev: 530e01e79e9674d0049b183dc23491eb886b066b) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working getgroups()André Draszik
recent coreutils (gnulib) assume yes when cross-compiling for gnu (glibc), but don't know about musl. For coherence, just set the result to yes for both. Note that the old coreutils (from meta-gplv2) doesn't assume anything and instead that recipe hard-codes to yes. So behaviour with yocto when using meta-gplv2 is actually better than when using the latest version (when using musl). This patch rectifies this shortcoming. (From OE-Core rev: 692fe85264e599eb659456bd2eebf5f12a1cd30f) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: set getcwd() test result for abort()-bug for glibc / muslAndré Draszik
This coreutils (gnulib) test checks for an abort() that existed in glibc before 2.4.90-10 (in 2006) in certain conditions. Neither libraries exhibit this problem today. (From OE-Core rev: 506c3b5adaa2fdffa051d83fb99efc00e432156b) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: set getcwd() behaviour for long paths for glibc / muslAndré Draszik
In glibc, getcwd() handles long file names properly, on musl, getcwd() only works up to PATH_MAX directory depths. Configuring the autotools (gnulib) test result here allows coreutils to compile more optimised code for both platforms, rather than being pessimistic and re-implementing everything itself. The difference in behaviour is because both do the kernel getcwd syscall (which only supports up to PATH_MAX), but glibc implements fallbacks for longer paths, while musl doesn't. (From OE-Core rev: 525e33cf99983ee4bc3cf1822364123551aa7c83) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have glibc compatible getcwd()André Draszik
I.e. allocate memory for the pointer returned when the first argument is NULL. (From OE-Core rev: fe148da36af2dc086e05e2ebc1c088f1b5485de2) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: linux supports unlink() of executing programAndré Draszik
I.e. shared text that is being executed. (From OE-Core rev: 1370742d20aaa1a17f3e242ea9bb54df944b6416) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have glibc compatible calloc()André Draszik
calloc (N, S) returns non-NULL when N*S is zero, and returns NULL when N*S overflows. (From OE-Core rev: ba2bc4b6529013a303dd67abe944ceb619e7466c) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl and glibc have working mkstemp()André Draszik
their mkstemp() passes all tests from the gnulib m4 macro gl_FUNC_MKSTEMP. (From OE-Core rev: 2b0905d25fa295fc868bf6df1da89283b9dc1f45) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: musl has working memcmp()André Draszik
I.e. a memcmp() that is 8bit clean (like glibc). (From OE-Core rev: d938ca1b8bc715047d771907c6ea4a1c9aa6594f) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11site: linux has working chown()André Draszik
I.e. a chown() that works when given -1 as uid / gid (From OE-Core rev: 226b8b2b1b565ef019b442ad3bf1f5d86704e1d2) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11busybox: Update inittabKhem Raj
Add stdin/stdout/stderr symlinks in case when not using hotplug Disable ctrl+alt+del, not used much Mount swap if defined (From OE-Core rev: b1799bd40dfa3b244ddf2b7fba1fb4dc1f9a7394) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-11perl: improve reproducibilityRoss Burton
Occasionally the reproducibility selftest fails because perl-pod differs, specifically that the perltoc.pod file was sometimes missing modules. Debugging revealed that there are missing dependencies so there is a build race: building perltoc.pod from an clean build tree results in no modules being listed at all. A bug has been filed at https://github.com/arsv/perl-cross/issues/86 to solve this properly, but for now we can just delete perltoc.pod after make has finished and re-generate it. [ YOCTO #13726 ] (From OE-Core rev: 7e0f6c9ea4f824f29dc30c6631fd8039ebe83a0b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10runqemu: Add network bridge supportJoshua Watt
Qemu supports attaching the virtual machine to an existing network bridge interface via the qemu-bridge-helper program (as long as the system is correctly configured to give the user permissions). Add support for runqemu to do this also via the "bridge=<INTERFACE>" argument. Note that for this to work correctly, the host qemu-bridge-helper must be used, not the one that might have been built by qemu-native. In order for qemu to correctly find this program, a qemu-oe-bridge-helper program has been added to qemu-helper-native, and runqemu will use this helper as the bridge helper. The helper will look for the host qemu-bridge-helper first by looking in the QEMU_BRIDGE_HELPER environment variable, then by search common paths where the helper is installed. (From OE-Core rev: 9e7b38c61c6b84b7f137c733ac5da9414025693d) Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10cups: fix crossscriptsDiego Rondini
Fix crossscripts to report the correct "serverbin" value. While the packaged "cups-config --serverbin" reported "/usr/libexec/cups" the crossscripts version reported "/usr/lib/cups", causing packaging issues when building for example cups-filters. Also fix FILES_${PN} to use ${libexecdir}; previously it was working just because "${libexecdir}/*" was part of the default values in bitbake.conf. (From OE-Core rev: 2ce6ef29b9bb4f16ed9d78e166d455b7a6d968bf) Signed-off-by: Diego Rondini <diego.rondini@kynetics.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10opensbi: Use -ffreestanding compiler optionsKhem Raj
This usually helps compiler to not use built-in optimizations for string functions and mem* functions unnecessarily, since OE's compiler is hosted for linux cross compile, this also means we instruct it rightly for building a baremetal application Refresh the patches to apply without fuzz Fixes linking errors e.g. platform/qemu/virt/lib/libplatsbi.a(sbi_string.o): in function `sbi_memset': | /mnt/b/yoe/build/tmp/work/riscv64-yoe-linux/opensbi/0.5-r0/git/lib/sbi/sbi_string.c:102: undefined reference to `memset' | collect2: error: ld returned 1 exit status (From OE-Core rev: f599b6c77f3585c8917f4d685689da4cc8a8bf04) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10Revert "tclibc-musl: Add -D__USE_TIME_BITS64 to c/c++ flags"Khem Raj
This reverts commit 194bd4136459e7a38510830b2fb0938d892ece45. __USE_TIME_BITS64 is already added by musl headers internally now [1] [1] https://git.musl-libc.org/cgit/musl/commit/include/alltypes.h.in?id=f12bd8e05c8bb2c3e2b91d635887ec424ef8fbd9 (From OE-Core rev: 2bc3f51a7151880fc7e27abf1762fb43f4e8fe54) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10alsa-plugins: 1.1.9 -> 1.2.1Tanu Kaskinen
(From OE-Core rev: 6ae82bd7ed6beece2fff8d83adcd86fc91cd8915) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10alsa-utils: 1.1.9 -> 1.2.1Tanu Kaskinen
I moved the ALLOW_EMPTY line next to the line that sets FILES to "". That makes it easier to see that the package is not only allowed to be empty, but forced to be empty. (From OE-Core rev: c6bb27bee2f6f3f363893e59de0373d1532519e8) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10alsa-topology-conf: new recipe, version 1.2.1Tanu Kaskinen
The topology configuration files were moved from the alsa-lib repository to a new alsa-topology-conf repository. The move was accompanied by a license change from LGPL2.1 to BSD-3-Clause. (From OE-Core rev: 4dd61230a6d2cc8183a12edc9834cb506b488e3a) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10alsa-ucm-conf: new recipe, version 1.2.1.2Tanu Kaskinen
The UCM configuration files were moved from the alsa-lib repository to a new alsa-ucm-conf repository. The move was accompanied by a license change from LGPL2.1 to BSD-3-Clause. (From OE-Core rev: 769354b372a4a60dfec921789d875340b0244406) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10alsa-lib: 1.1.9 -> 1.2.1.2Tanu Kaskinen
Changelogs: https://alsa-project.org/wiki/Changes_v1.1.9_v1.2.1 https://alsa-project.org/wiki/Changes_v1.2.1_v1.2.1.1 https://alsa-project.org/wiki/Changes_v1.2.1.1_v1.2.1.2 This upgrade brings support for the new "UCM2" configuration format. Another big change is that the UCM and topology configuration files were moved to separate repositories, so those are removed from alsa-lib and will need to be packaged separately. The topology API was moved from libasound to a separate libatopology library. This seems like a recipe for regressions for applications that used to use libasound for the topology stuff, but I don't think there are many applications in existence that use the topology API. I hope the upstream knows what they are doing. Patches added: 0001-configure.ac-remove-an-unnecessary-libtool-fix.patch This fixes a failure during configure. 0001-ucm-Use-strncmp-to-avoid-access-out-of-boundary.patch 0002-ucm-return-always-at-least-NULL-if-no-list-is-availa.patch Backports. I don't know if these are regression fixes, but since the UCM code was heavily worked on in this upgrade, it seems likely that these patches fix regressions. 0003-namehint-correct-the-args-check.patch 0004-namehint-improve-the-previous-patch-check-the-return.patch Backports. A change in alsa-plugins caused a regression in the pulse plugin, but that was actually due to a bug in alsa-lib, which is fixed by these patches. 0005-ucm-Do-not-fail-to-parse-configs-on-cards-with-an-em.patch Backport. Fixes a regression with some Intel hardware. 0001-Fix-alsa-sound-.h-for-external-programs.patch 0001-uapi-Move-typedefs-from-uapi-to-sound.patch Backports. These fix build failures in alsa-tools. I removed alsa-doc from PACKAGES, because no files were assigned to it. (From OE-Core rev: 966890009b4dd81abb72534192c688dbd1195d00) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10ovmf: update to 201911Alexander Kanavin
Remove unused patch. (From OE-Core rev: 159328dde56e35ba56ec0b1e3602a3b2df6ad691) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10populate_sdk_ext.bbclass: No longer needed to clean away conf/sanity_infoPeter Kjellerstedt
Since the sanity_info file has moved from the conf directory to the cache directory, there is no longer any need to clean it away explicitly in clean_esdk_builddir() since the whole cache directory is already cleaned away anyway. (From OE-Core rev: 40c30990e1be72130819c040fe471e2bdc0c6e7d) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10sanity.bbclass: Move sanity_info from conf to cachePeter Kjellerstedt
Since this file is written during recipe parsing, having it in the ${BUILDDIR}/conf directory, which is covered by an inotify watcher, will trigger a re-parse the next time bitbake is run and the resident bitbake server is enabled. This causes the sanity_info file to be updated again, which triggers a new parse the next time bitbake is run ad infinitum. Moving it to ${BUILDDIR}/cache should avoid this. (From OE-Core rev: f98103b548aa7dba6b1be6c8e02ef41858a8e85c) Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10zip: Add patch fixing zipnote segfaultJate Sujjavanich
This patch has been applied in several Linux distributions (From OE-Core rev: 8e662fced80c98c5495d49c905cc0008cb812589) Signed-off-by: Jate Sujjavanich <jatedev@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10speexdsp: 1.2rc3 -> 1.2.0Tanu Kaskinen
Removed backported patch 0001-Don-t-rely-on-HAVE_STDINT_H-et-al.-being-defined.patch Enabling NEON on aarch64 doesn't break the build any more. (From OE-Core rev: f715c3cd1342a19a9cb780d02dfa425721b456be) Signed-off-by: Tanu Kaskinen <tanuk@iki.fi> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10enchant: Replace with enchant2 from meta-oeAdrian Bunk
webkitgtk does now support the new version. (From OE-Core rev: aca863fc4259863d6841b25649c6718c64ccfe6b) Signed-off-by: Adrian Bunk <bunk@stusta.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10oeqa: archiver: Tidy up test case descriptionsPaul Barker
(From OE-Core rev: 8f9119cb1451ef6337b98e4bb566069aa8d66a35) Signed-off-by: Paul Barker <pbarker@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10archiver.bbclass: Add new mirror archiver modePaul Barker
We define a new method of populating a source mirror using the archiver bbclass instead of simply copying the contents of the downloads directory. This allows the archiver features such as copyleft license filtering and recipe type filtering to be used when preparing a source mirror. This new archiver mode is selected by setting `ARCHIVE_MODE[src]` to 'mirror'. The source mirror mode can either be 'split' (default) or 'combined', controlled by `ARCHIVER_MODE[mirror]`. Additionally, sources can be excluded as needed by setting `ARCHIVER_MIRROR_EXCLUDE` to a list of URI prefixes. These options are described in more detail in the new entries in the header of archiver.bbclass. New oeqa selftest cases are added to cover the mirror archiver mode. (From OE-Core rev: 2c8b31ae0ab95a8b100e8bade23f51574e273c9a) Signed-off-by: Paul Barker <pbarker@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10openssh: Allow clock_nanosleep/clock_gettime64/clock_nanosleep_time64 syscallKhem Raj
Fixes connection denials with these syscalls being there on upcoming glibc 2.31 release (From OE-Core rev: 557d464de217cdf959aa275d20e7b155e4130ec7) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2020-01-10maintainers.inc: cleanup entriesYi Zhao
Cleanup the following entries because these recipes have been removed from oe-core: cve-check-tool gcc-cross-initial gcc-crosssdk-initial gcc-source-8.3.0 gccmakedep gnome-themes-standard gtk+ gtk-icon-utils-native libnewt-python mkfontdir python3-file-utils (From OE-Core rev: 993d6033fc11f698f328378d465889ff5d781aa0) Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-03 00:36:44 +0000