summaryrefslogtreecommitdiffstats
path: root/meta
Commit message (Collapse)AuthorAgeFilesLines
* ofono: upgrade 1.31 -> 1.32Richard Purdie2021-05-181-2/+1
| | | | | | (From OE-Core rev: c0e635c85b2d1eedcc515a89e949b8c9e43d8881) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: update patch statusRoss Burton2021-05-171-1/+1
| | | | | | | (From OE-Core rev: 87f0b45a307bb47df5a68d6649fe5625f2dd0775) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-jinja2: Upgrade 2.11.3 -> 3.0.0Richard Purdie2021-05-161-1/+1
| | | | | | (From OE-Core rev: 1e520a7d0602059101646f24e7e347e4117697e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-markupsafe: Upgrade 1.1.1 -> 2.0.0Richard Purdie2021-05-161-2/+1
| | | | | | (From OE-Core rev: def6184a8f24fe8965db77511bbc65edb38942c2) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Upgrade 5.2.0 -> 6.0.0Richard Purdie2021-05-1647-2670/+99
| | | | | | | | | | | | | Building without PIE support seems broken upstream, enable it by default to match the configuration others evidently use. Tweak git submodule option to match upstream. Drop backported/merged patches, refresh others. (From OE-Core rev: ede1b86e663f1cafccc8aa8c35fa13ebd3f55d11) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-ust: Upgrade 2.12.1 -> 2.12.2Richard Purdie2021-05-161-2/+1
| | | | | | (From OE-Core rev: 03b9c9ab5e74c4e825a023e54fe8891f6f6cc809) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: update to v2.12.6Bruce Ashfield2021-05-168-781/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To support building against v5.12+ and v5.13+ kernels, bumping to the v2.12.6 lttng-release. We drop the previously backported patches, and bring in the following commits: 0d8e4ab9 Version 2.12.6 78f56ae3 fix: adjust ranges for RHEL 8.2 and 8.3 4c996ea7 Disable block rwbs bitwise enum in default build 4ac46085 Disable sched_switch bitwise enum in default build 5e22c27b Add experimental bitwise enum config option 937d307e Add defaults to Kconfig options 4a114d43 Sync `show_inode_state()` macro with upstream stable kernels 3bd6ac3e fix: block: remove disk_part_iter (v5.12) 8bbb8c9d Fix: Backport of "Fix: increment buffer offset when failing to copy from user-space" 30cddf69 Fix: increment buffer offset when failing to copy from user-space 4733b9ab Sync `show_inode_state()` macro with Ubuntu 4.15 kernel ff21ec48 fix: mm, tracing: kfree event name mismatching with provider kmem (v5.12) b2b02c29 Set 'stable-2.12' branch in git review config 00b42dbf fix backport: block: add a disk_uevent helper (v5.12) 771ff089 fix: Adjust ranges for Ubuntu 5.4.0-67 kernel d8933959 fix: block: add a disk_uevent helper (v5.12) 71034df1 Fix: properly compare type enumeration 4d879d23 compiler warning cleanup: is_signed_type: compare -1 to 1 fead3a9c Fix: bytecode linker: validate event and field array/sequence encoding 92cc3e7f Fix: kretprobe: null ptr deref on session destroy 49c603ef fix: mm, tracing: record slab name for kmem_cache_free() (v5.12) 23a2f61f Fix: filter interpreter early-exits on uninitialized value b3fdf78b Fix: memory leaks on event destroy (From OE-Core rev: c2f027b8e2f842915a0ffdfd6c2c0597f3b02bce) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* lttng-modules: update devupstream to v2.13-rcBruce Ashfield2021-05-162-5/+42
| | | | | | | | | | | | | | | | To support builds against v5.13+ kernels, bumping the devupstream to 2.13 and the 2.13-rc series. Along with the SRCREV update, a port of the existing CONFIG_TRACEPOINTS patch from the main Makefile to src/Kbuild is done. The LICENSE file was part of commit [Cleanup: Move headers from toplevel to include/lttng/], so we adjust the checksum to the new fie contents. (From OE-Core rev: 18bf7b0eafc5331b0b33c0ae777374e24df741b8) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libnotify: Make gtk+3 dependency optionalMike Crowe2021-05-161-3/+6
| | | | | | | | | | | | | | | | | | libnotify only requires gtk+3 for its tests. Let's disable them by default and only enable them if "tests" is in PACKAGECONFIG. If gtk+3 is not available then we need to declare the dependency on gdk-pixbuf explicitly. It looks like the tests genuinely do need some sort of desktop environment to run, so let's maintain the ANY_OF_DISTRO_FEATURES check added back in 3edf08b38b0af93cef0933b061349264dc86d54c. (From OE-Core rev: da15d7cf3e6f31c92232f8dd7272ea9ee41656db) Signed-off-by: Mike Crowe <mac@mcrowe.com> Cc: Khem Raj <raj.khem@gmail.com> Cc: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sstate: Handle manifest 'corruption' issueRichard Purdie2021-05-161-1/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Under certain build patterns, warnings about missing manifests can appear. These are real issues where the manifest was removed and shouldn't have been. Martin Jansa was able to find a reproducer of: MACHINE=qemux86 bitbake zlib-native echo 'PR = "r1"' >> meta/recipes-core/zlib/zlib_1.2.11.bb MACHINE=qemux86-64 bitbake zlib-native MACHINE=qemux86 bitbake zlib-native <the zlib-native manifest is now removed along with the sysroot-components contents> The code maintains a per machine list of stamps but a per PACAGE_ARCH list of stamp/manifest/workdir mappings. The latter is only appended to for speed with the assumption that once stamps are gone, the code wouldn't trigger. The code only ever appends to the mapping list (for speed/efficency under lock) meaning that multiple entries can result where the stamp/workdir differs due to version changes but the manifest remains the same. By switching MACHINE part way through the build, the older stamp is referenced and the manifest is incorrectly removed as it matches an now obsolete entry in the mapping file. There are two possible fixes, one is to rewrite the mapping file every time which means adding regexs, iterating and generally complicating that code. The second option is to only use the last mapping entry in the file for a given manifest and ignore any earlier ones. This patch implments the latter. Also drop the stale entries if we are rewriting it. (From OE-Core rev: 63da9a4f889c5b0e41bc8ec08abe0acea1546479) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sysklogd: upgrade 2.2.2 -> 2.2.3zhengruoqin2021-05-161-1/+1
| | | | | | | (From OE-Core rev: a366a457bf0c990df4bb97cfc5477dbc75eaff65) Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpcbind: upgrade 1.2.5 -> 1.2.6zhengruoqin2021-05-162-31/+30
| | | | | | | | | refresh rpcbind_add_option_to_fix_port_number.patch (From OE-Core rev: 11bbe1c86d5d3e446fe5ea4028bc8b3f21b98587) Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rng-tools: upgrade 6.11 -> 6.12zhengruoqin2021-05-161-1/+1
| | | | | | | (From OE-Core rev: 5af1d25d9621020d89c1193e0f95fefa1be85642) Signed-off-by: Zheng Ruoqin <zhengrq.fnst@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-loader: upgrade 1.2.170.0 -> 1.2.176.0wangmy2021-05-161-1/+1
| | | | | | | (From OE-Core rev: b87917335c252a38ea63f999b9d3611ac079104b) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-tools: upgrade 1.2.170.0 -> 1.2.176.0wangmy2021-05-161-2/+2
| | | | | | | (From OE-Core rev: 8c864d0711a39548b69c7ea278f2d978651925e7) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-headers: upgrade 1.2.170.0 -> 1.2.176.0wangmy2021-05-161-1/+1
| | | | | | | (From OE-Core rev: 4ebbb906227f31548e708bd01c54407f3221c63e) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* vulkan-samples: update to latest revisionwangmy2021-05-161-1/+1
| | | | | | | (From OE-Core rev: e59138cc1ee028e19b00ced57da33ab348c367cf) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-six: upgrade 1.15.0 -> 1.16.0wangmy2021-05-162-5/+4
| | | | | | | (From OE-Core rev: c27ede9d77edc0a0ca71707642f19e43fe9c4e7d) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3-attrs: upgrade 20.3.0 -> 21.2.0wangmy2021-05-161-2/+1
| | | | | | | (From OE-Core rev: f6e624046afbbf6853c7fe409f77ecd2ab802f21) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* npm.bbclass: Allow nodedir to be overridden by NPM_NODEDIRMike Crowe2021-05-141-2/+4
| | | | | | | | | | | | Node modules may need to be built against multiple Node versions. Setting nodedir in the NPM configuration stops older ways of doing this, such as setting npm_config_target and npm_config_disturl, from working. (From OE-Core rev: 14795ee305f3c11fcc31cc7ca815b8ff1020e29a) Signed-off-by: Mike Crowe <mac@mcrowe.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* nativesdk-meson: correctly set cpu_familyAlexander Kanavin2021-05-141-12/+2
| | | | | | | | | | This was a warning before, but with the patch that turns it into an error, it needs to be properly addressed. (From OE-Core rev: b6257f3b88e788af3ee748a8a6366aab819dce3f) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: backport a patch to fix meson 0.58 buildsAlexander Kanavin2021-05-142-0/+54
| | | | | | | (From OE-Core rev: fe6889ed05edf2f1e4ac7b06debd4cc43ebb9607) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson: update 0.57.2 -> 0.58.0Alexander Kanavin2021-05-1410-98/+456
| | | | | | | | | | | | | Rebase patches; dropped chunks (and cross-prop-default.patch) have been removed upstream. Move native-only patches to all-patches, as they're a pain to rebase separately. (From OE-Core rev: cb2a7dcc86d784cb9903f69570ddc05e23d36529) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gstreamer1.0-plugins-base: backport a patch to fix meson 0.58 buildsAlexander Kanavin2021-05-142-0/+51
| | | | | | | (From OE-Core rev: 4e509099d1a8c22e5f592e6675dabacfe910b9b9) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meson.bbclass: split python routines into a separate classAlexander Kanavin2021-05-142-51/+52
| | | | | | | | | This allows reusing them in nativesdk-meson without copy-pasting code. (From OE-Core rev: f2715f5f2a56f9b660f9f0fe2933ec231a2dd8c0) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* expat: upgrade 2.2.10 -> 2.3.0Alexander Kanavin2021-05-143-89/+5
| | | | | | | | | | | | | Drop 0001-Add-output-of-tests-result.patch (difficult to rebase). I have verified that ptests still pass, and print PASS for every test. If they start failing we can revisit what kind of output would be beneficial. (From OE-Core rev: ef1a76f9c130e7efaecae15ccb1d48a03fa17b9b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gnome: drop upstream even condition from a few recipesAlexander Kanavin2021-05-144-4/+4
| | | | | | | | | | | They have adopted the new gnome version scheme where the distinction is no longer: https://lwn.net/Articles/831746/ (From OE-Core rev: 7e36fe212eb6bc9a4dbe66007837ad87d8f00a7d) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* gdk-pixbuf: rewrite the cross-build support for testsAlexander Kanavin2021-05-146-194/+176
| | | | | | | | | | | It was scattered over four different patches, and wasn't guarded by a configuration option. Hopefully the new patch is acceptable to upstream. (From OE-Core rev: 92fc28498fcb9bdcea743961729b21b7e6c6b1fa) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* go: upgrade 1.16.3 -> 1.16.4wangmy2021-05-148-4/+4
| | | | | | | (From OE-Core rev: 1e280a596293976ac835b557dcaaa56972682480) Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* npth: Check for pthread_create for including lpthreadKhem Raj2021-05-142-0/+44
| | | | | | | | | | | pthread_detach() is moved into libc which means this test will fail so check for pthead_create again [1] https://sourceware.org/git/?p=glibc.git;a=commit;h=df65f897e9501aa5b64a5cbcb101301715f2ec2f (From OE-Core rev: e82742849e6228f892a489bfbd02c365c4a8607e) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* python3: upgrade 3.9.4 -> 3.9.5Trevor Gamblin2021-05-141-1/+1
| | | | | | | | | Version 3.9.5 includes a fix for CVE-2021-29921. (From OE-Core rev: be23351f97c1a7362c0ddd240a6de0cddfca1b01) Signed-off-by: Trevor Gamblin <trevor.gamblin@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: disable gtk bitsAlexander Kanavin2021-05-141-1/+1
| | | | | | | | | | | This should greatly reduce dependency chains on the autobuilder; the only affected recipe is remmina, where avahi support will be disabled by default. (From OE-Core rev: 5f68f2e72accecaad6210c71d7f1ffb069edf011) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* meta/lib/oe/rootfs.py: Fix typo "Restoreing" -> "Restoring"Robert P. J. Day2021-05-131-1/+1
| | | | | | | (From OE-Core rev: 2621dbbc1181808f18ca4ae79408d0d5b557670f) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image.bbclass: fix comment "pacackages" -> "packages"Robert P. J. Day2021-05-131-1/+1
| | | | | | | (From OE-Core rev: 5c5f0d21799c2bff6875ef9fdc22d11035ea3320) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu-x86: Add commandline options to improve bootRichard Purdie2021-05-131-1/+1
| | | | | | | | | | To try and help with the inermittent rcu stalls and boot issues with qemu add some kernel commandline options commonly used with qemu instances which were suggested may help. (From OE-Core rev: d75cb16ecb3a55fd7631bf7720663e4b196421ee) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemuboot-x86: Switch to IvyBridge and q35 instead of pcRichard Purdie2021-05-131-4/+4
| | | | | | | | | | | | | | | | Move from 1996 to 2009 by swapping machine 'pc' for 'q35'. Also move to a CPU which is SMP capable and doesn't have tsc bugs. IvyBridge matches what we're using on the autobuilder. The intent here is to try and improve on some of the intermittent autobuilder issues we're seeing. I'm told that nobody else runs with config this old and it could well be contributing to our issues. Having reliable testing is key to the project and justifies updating this IMO. (From OE-Core rev: 6d9f25782bd585e89c5aaf7046266c848f1e581b) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: Set SMP to 4 cpus for arm/x86 onlyRichard Purdie2021-05-134-1/+4
| | | | | | | | | | Only qemux86* and qemuarm* support SMP with our current configurations so rework qemu SMP enabling to account for that and only use it on the architectures where it works. (From OE-Core rev: ee371325ce651cc113e43bdeb5d8986d5b84a3f4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qemu: use 4 cores in qemu guestsAlexander Kanavin2021-05-131-0/+4
| | | | | | | | | | Each of the cores is mapped to a thread on the host, this should speed up things inside qemu which can take advantage of that. (From OE-Core rev: 56f98d12a79585a4d4c459160f39403e05b620a5) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* btrfs-tools: Update to 5.12Robert Joslyn2021-05-131-3/+4
| | | | | | | | | | | | Add PACKAGECONFIG for zoned block devices. Leave disabled by default, as this requires a recent kernel. License-Update: libbtrfsutil was relicensed to LGPLv2.1+: https://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git/commit/?id=9e30f779e3cbf12a88ebe309ee371851fdfd3aa0 (From OE-Core rev: d10b62f54c6e0f19af02bab024680462d9e4418a) Signed-off-by: Robert Joslyn <robert.joslyn@redrectangle.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* binutils: backport DWARF-5 support for goldMartin Jansa2021-05-132-0/+1375
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * DWARF-5 is now used by default with gcc-11, causing 11.1.0/ld: internal error in format_file_lineno, at ../../gold/dwarf_reader.cc:2278 collect2: error: ld returned 1 exit status in various projects (runc-opencontainers, libhybris, collada-dom) * https://gcc.gnu.org/gcc-11/changes.html For targets that produce DWARF debugging information GCC now defaults to DWARF version 5 (with the exception of VxWorks and Darwin/Mac OS X which default to version 2 and AIX which defaults to version 4). This can produce up to 25% more compact debug information compared to earlier versions. To take full advantage of DWARF version 5 GCC needs to be build against binutils version 2.35.2 or higher. When GCC is build against earlier versions of binutils GCC will still emit DWARF version 5 for most debuginfo data, but will generate version 4 debug line tables (even when explicitly given -gdwarf-5). The following debug information consumers can process DWARF version 5: GDB 8.0, or higher valgrind 3.17.0 elfutils 0.172, or higher (for use with systemtap, dwarves/pahole, perf and libabigail) dwz 0.14 Programs embedding libbacktrace are urged to upgrade to the version shipping with GCC 11. To make GCC 11 generate an older DWARF version use -g together with -gdwarf-2, -gdwarf-3 or -gdwarf-4. (From OE-Core rev: d07d4d739ae17787017f771dd2068fda0e836722) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* libarchive: disable redundant libxml2 PACKAGECONFIGRoss Burton2021-05-131-1/+0
| | | | | | | | | | | | | | An XML parser (either libxml2, or expat) is only needed by libarchive to read/write XAR archives. However, these also need OpenSSL enabled which by default it is not, so XAR files were disabled and libxml2 was a build dependency for no reason. As XAR archives are mainly used on macOS, we can remove libxml2. (From OE-Core rev: 363f1ee30b0e6d222943aaed8dce37a4a441a86d) Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* webkitgtk: fix build without opengl in DISTRO_FEATURESMartin Jansa2021-05-132-0/+38
| | | | | | | (From OE-Core rev: 3b46038685c4d319ca0c88b3519cde04d615dc2a) Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* avahi: Exclude CVE-2021-26720 from cve-checkRichard Purdie2021-05-131-0/+3
| | | | | | | | Issue only affects Debian and SUSE. (From OE-Core rev: 72522fa1a5f3b9b2855043fe6b421886d641385f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* librsvg: Exclude CVE-2018-1000041 from cve-checkRichard Purdie2021-05-131-0/+3
| | | | | | | | Issue only affects windows. (From OE-Core rev: a90d3b056992346003d96765fc8639f5235cca55) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* coreutils: Exclude CVE-2016-2781 from cve-checkRichard Purdie2021-05-131-0/+4
| | | | | | | | | | | http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=v8.27-101-gf5d7c0842 "Given runcon is not really a sandbox command, the advice is to use `runcon ... setsid ...` to avoid this particular issue. (From OE-Core rev: 2d273b5aed4a5bd509ec9c68a6f451c17ec17d0c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* rpm: Exclude CVE-2021-20271 from cve-checkRichard Purdie2021-05-131-0/+4
| | | | | | | | | This is included in the release we have, it was the reason for the last rpm point release. (From OE-Core rev: 117feb358c81b6b852dee24268eac0a1a47c1701) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* kern-tools: Kconfiglib: add support for bare 'modules' keywordBruce Ashfield2021-05-131-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Bumping the SRCREV to pickup the following for the kern-tools: commit 6dd85ff178cd76851e2184b13e545f5a88d1be30 [kconfig: change "modules" from sub-option to first-level attribute] broke parsing in 5.13+ trees. We add the new location to the parser so we can support both types of module specifications. Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Without this, the kernel configuration audit for 5.13+ errors immediately. The older "option modules" parsing has been left in the code, so that older kernels continue to work as well. (From OE-Core rev: ba39e42681e7e3c6fe82686a42a9ee4b519003f9) Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: Fix other reproducibility issuesRichard Purdie2021-05-132-0/+166
| | | | | | | | | When building in longer paths, the ovmf build changes in many ways. This adds a patch addressing various causes of problems. Full details are in the patch header. (From OE-Core rev: 9113a5815f3c682ef99fd777e35e892b2e08237f) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ovmf: Disable lto to aid reproducibilityRichard Purdie2021-05-131-1/+8
| | | | | | | | | | lto tends to break reproducibility and makes ovmf near impossible to debug reproducibility issues in. Disable it and supress the warnings that then generates from Werror. (From OE-Core rev: 627b6ed763eca90192203932784872b60a65fcaa) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ffmpeg: Fix build on mipsKhem Raj2021-05-121-7/+15
| | | | | | | | | | | | | | | | | configure is not able to decode, right options to compiler, it needs to be set according to default tune manually. Fixes build issue on mips e.g. {standard input}: Assembler messages: | {standard input}:2162: Error: opcode not supported on this processor: mips32r2 (mips32r2) `dmult $22,$22' | {standard input}:2164: Error: opcode not supported on this processor: mips32r2 (mips32r2) `dsrl $5,$5,32' | make: *** [/mnt/b/yoe/master/build/tmp/work/mips32r2-yoe-linux/ffmpeg/4.4-r0/ffmpeg-4.4/ffbuild/common.mak:67: libavcodec/aptxenc.o] Error 1 (From OE-Core rev: b254db634fc888ae75e843c8a9108e71ffff3f77) Signed-off-by: Khem Raj <raj.khem@gmail.com> Cc: Alexander Kanavin <alex.kanavin@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-07-04 03:14:46 +0000