summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2021-02-25socat: Exit when the file associated with an FD is destroyedrbt/socatRobert Yang
In many scenarios the receipt of an EOF will coincide with the teardown of the file which the FD is associated with by the application on the other side of the file pipe. If a timeout (-t) is used socat continues to poll for new data (read) and send any new data (write) until the timeout. This can lead to input/output errors as the FD exists still but the file it was openned on is gone, and no check is done on writes. To get around this a check is added after the EOF is received that the file still exists, and if not we proceed to exit immediately. This will avoid i/o errors and will also cause a quicker return as we don't have to wait for the timeout. The original author is Mark Asselstine <asselsm@gmail.com>. Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
2021-02-24diffoscope: Ensure rpm is configured correctlyRichard Purdie
diffoscope was failing as rpm wasn't configured correctly. Fix this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-24selftest/reproducible: Remove exclusions for recipes which now reproduceRichard Purdie
git, libproxy, libcap-ng(-python), babeltrace2, rsync and groff have their reproducibility issues fixed, remove from the exclusion list. Also fix whitespace. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-24bitbake.conf: Introduce FAKEROOTLOGS variable used by bitbake to print ↵Tomasz Dziendzielski
pseudo.log Bitbake depends on this variable while looking for pseudo.log file in case of fakeroot task failure. Signed-off-by: Tomasz Dziendzielski <tomasz.dziendzielski@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-24diffoscope: Add python3-rpm as dependencyJoshua Watt
The python3-rpm package is required for diffoscope to diff RPM packages Signed-off-by: Joshua Watt <JPEWhacker@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-24reproducible: Improve SOURCE_DATE_EPOCH_FALLBACK handlingRichard Purdie
Ensure the fallback value if used is written to the SDE file and hence stored in sstate, reducing any confusion within the code over '0' values. Bump the HASHEQUIV_VERSION since we've had a ton of trouble with ensuring this rolls out correctly on the autobuilder so others may too, take a clean slate for it. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-24reproducible_builds: SOURCE_DATE_EPOCH should not be 0Jan-Simon Möller
A SOURCE_DATE_EPOCH of 0 might be misinterpreted by namely rpm as no SDE. e.g.: char *srcdate = getenv(SOURCE_DATE_EPOCH); if (srcdate && rpmExpandNumeric(%{?clamp_mtime_to_source_date_epoch})) Solve this by: - providing a SOURCE_DATE_EPOCH_FALLBACK variable != 0 - changing defaults to use it - using SOURCE_DATE_EPOCH_FALLBACK also when reading 0 out of sstate-cache Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23babeltrace2: Fix reproducibilityRichard Purdie
babeltrace2-ptest was referencing the host's python version in it's makefiles. Whilst this could be fixed, its easier to correct the python version being found to the target one which works much more effectively and solves the issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23diffoscope: Ensure the correct magic file is usedRichard Purdie
diffoscope uses libmagic and it was searching in file-native's sysroot for the magic file. Wrap it and set MAGIC in the environment to ensure the file is found correctly and avoid build failures. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23report-error.bbclass: Add layer and bitbake version info to error reportMilan Shah
Instead of just providing local.conf info, add layer names and their revisions with bitbake version information into error report makes it easier to understand and reproduce failed build. [YOCTO #9700] Signed-off-by: Milan Shah <mshah@mvista.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23kernel-fitimage: Don't use unit addresses on FITKlaus Heinrich Kiwi
Das U-Boot 2021.4-rc1 has the following commit: commit 3f04db891a353f4b127ed57279279f851c6b4917 Author: Simon Glass <sjg@chromium.org> Date: Mon Feb 15 17:08:12 2021 -0700 image: Check for unit addresses in FITs Using unit addresses in a FIT is a security risk. Add a check for this and disallow it. CVE-2021-27138 Adjust the kernel-fitimage.bbclass accordingly to not use unit addresses. This changte is required before we can bump U-Boot to 2021.4. Signed-off-by: Klaus Heinrich Kiwi <klaus@linux.vnet.ibm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23grub: shuffle packaging for aarch64 buildsRoss Burton
Even in grub-efi platforms we need to build grub for the the common tools. On x86 this isn't a problem because grub builds legacy boot and grub-efi builds EFI, but on aarch64 there is no legacy boot supported by grub. To ensure that the common tools are built the grub recipe also builds EFI binaries, but this now means that grub and grub-efi ship the same binaries. oe-core 933286 fixed this conflict by deleting the binaries from grub-efi and putting the aarch64 modules into grub-common (relying on dependencies to pull grub-common in). This seems backwards: grub-efi no longer contains the binaries and they're in different packages on arm or x86. Also, SDK generation is broken as the grub package itself is now empty as the binaries are in grub-common. Resolve all of these issues by reversing the logic: grub-efi is the package which holds the EFI binaries on all platforms. grub only builds for EFI on aarch64 as a way to build the common binaries, so delete them in that recipe to avoid conflicts. And finally as the grub recipe is empty on aarch64 but needed by dependencies, set ALLOW_EMPTY. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23python3: Fix python interpreter line length for nativesdkMingli Yu
Make sure the python interpreter is "#!/usr/bin/env python3" for nativesdk to avoid the shebang path exceeding the limit when install the sdk under the directory with long path. Before: $ cd ${target_sdk_dir} $ vi ./sysroots/x86_64-oesdk-linux/usr/bin/2to3 #!${target_sdk_dir}/sysroots/${SDK_SYS}/usr/bin/python3.9 [snip] After: $ cd ${target_sdk_dir} $ vi ./sysroots/x86_64-oesdk-linux/usr/bin/2to3 #!/usr/bin/env python3 [snip] Signed-off-by: Mingli Yu <mingli.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23screen: fix CVE-2021-26937Scott Murray
Apply patch from Debian to fix CVE-2021-26937. Signed-off-by: Scott Murray <scott.murray@konsulko.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23conf/machine-sdk: Add ppc64le SDK machineJoel Stanley
Previously SDKMACHINE would default to x86_64. Commit 539cd4a5fbb9 ("bitbake.conf: default SDKMACHINE to the build host architecture") changed it to default to the build machine, causing the build to fail on a ppc64le host. Reported-by: Andrew Geissler <geissonator@yahoo.com> Link: https://www.mail-archive.com/yocto@lists.yoctoproject.org/msg04364.html Signed-off-by: Joel Stanley <joel@jms.id.au> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23libpcre: Drop old/stale patchRichard Purdie
According to my tests this incorrect symbols resolution at runtime no longer happens. Ubuntu is still carrying the patch but also probably doesn't need to, they are also on a much older version. It sounds like there was once a linkage bug somewhere which has likely been resolved since. Drop the patch as it doesn't seem needed anymore. If it were a real issue it should be submitted upstream too, the status is incorrect. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23ca-certificates: Clean up two patches and submit upstreamRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23libevdev: Update patch status to backportRichard Purdie
The patch was submitted and merged upstream. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23libcap-ng: Replace python patch with a better fixRichard Purdie
By using the python3targetconfig class we can drop the existing python patch and the extra make parameters. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23libcap-ng: Fix python bindings determinism issueRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23rsync: Fix group name determinism issueRichard Purdie
configure falls back to inspecting the host#s /etc/group for the nobody/nogroup naming. Pass the correct value to configure to ensure host differences don't sneak in. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23rsync: Fix a file sorting determinism issueRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23libproxy: Avoid /etc/sysconfig determinism issueRichard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23tune-power9: Enable qemu-usermodeKhem Raj
With latest qemu it works ok Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23glibc: Build for power9 cpu when using powerpc64le tunesKhem Raj
This makes sure that we can compile glibc for powerp9 based machines irrespective of endianness or bitness Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23bitbake.conf: Do not use lib64 for baselib on musl/ppc64Khem Raj
musl is configured to use /lib and /usr/lib for ppc64 unlike glibc where it is expected to have libs in /lib64 and /usr/lib64 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23goarch.bbclass: Fix ppc64le detectionKhem Raj
ppc64le should go above ppc64 in checks otherwise it gets subsumed wrongly with ppc64 check Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23musl: Install /lib directoryKhem Raj
loader is installed into /lib and ${base_libdir} may not be always pointing to /lib, while here we want to create the directory where ldso will reside Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23linuxloader: Deal with little-endian ppc64 ldso nameKhem Raj
On ppc64le 'le' should be appended to ldso name Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23runqemu: Add new option to disable vga emulationKhem Raj
When using nographic, explicitly disabling vga is needed some cases since some qemu firmware (OpenFirmware ) defaults to std vga, and when vga is enabled then it disables output to serial and redirects that to vga which is by design, hwoever we expect the console output to go to serial when using nographic, therefore its important to disable vga with nographic especially on qemu based ppc platforms 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>
2021-02-23systemd: Fix importd requirements commentVivien Didelot
The comment above the importd config states curl, which does not exist in PACKAGECONFIG. Adding it results in the following error (and then misleading compilation failures): WARNING: systemd-1_244.5-r0 do_configure: QA Issue: systemd: invalid PACKAGECONFIG: curl [invalid-packageconfig] Support for curl is currently enabled through journal-upload: PACKAGECONFIG[journal-upload] = "-Dlibcurl=true,-Dlibcurl=false,curl" While it might be more appropriate to deprecate "journal-upload" in favor of a "curl" PACKAGECONFIG entry, simply fix the importd comment for now by stating upload-journal instead of curl. Signed-off-by: Vivien Didelot <vdidelot@pbsc.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23python3-magic: upgrade 0.4.18 -> 0.4.20Richard Purdie
License changed as there was additional copyright information added but the underlying license did not change. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23apt: Upgrade 1.8.2.1 -> 1.8.2.2Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23python3-pycryptodome/pycryptodomex: upgrade 3.9.9 -> 3.10.1Richard Purdie
The license file dropped the APL-2 pieces but this wasn't in LICENSE in the first place, no code seemed to refer to it so no change was needed. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23nettle: Upgrade to 3.7.1Khem Raj
bugfix release [1] [1] https://lists.gnu.org/archive/html/info-gnu/2021-02/msg00011.html Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23linux-firmware: upgrade 20201218 -> 20210208Richard Purdie
License file had a number of new additions for new firmware but no new licenses that didn't already exist. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23diffoscope: Upgrade 166 -> 167Richard Purdie
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23openssl: upgrade 1.1.1i -> 1.1.1jWang Mingyu
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23lttng-ust: upgrade 2.12.0 -> 2.12.1Wang Mingyu
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23liburcu: upgrade 0.12.1 -> 0.12.2Wang Mingyu
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23net-tools: update to 2.10Oleksandr Kravchuk
Removed upstreamed patches. Added new package configs. Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23ell: update to 0.38Oleksandr Kravchuk
Changelog: - Fix issue with DHCP v6 Rapid Commit option check. - Fix issue with handling RFC8018/RFC1423 padding. Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-23python3: update to 3.9.2Oleksandr Kravchuk
Removed CVE patch was upstreamed. License-Update: copyright years. Signed-off-by: Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21xkeyboard-config: upgrade 2.31 -> 2.32Wang Mingyu
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21util-linux: upgrade 2.36.1 -> 2.36.2Wang Mingyu
0001-build-sys-do-not-build-plymouth-ctrl.c-w-disabled-pl.patch 0001-hwclock-do-not-assume-__NR_settimeofday_time32.patch removed since they are included in 2.36.2 Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21glibc: Unify wordsize.h with arm multilibszhengruoqin
wordsize.h should be the same under arm and aarch64, othersise the following error happens: "file /usr/include/bits/wordsize.h conflicts between attempted installs of lib32-libc6-dev-2.33-r0.armv7ahf_neon and libc6-dev-2.33-r0.aarch64" Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21glibc-package.inc: Fix arm multlib header issue with struct_stat.hzhengruoqin
Fix build error under multilib as following: "file /usr/include/bits/struct_stat.h conflicts between attempted installs of lib32-libc6-dev-2.33-r0.armv7ahf_neon and libc6-dev-2.33-r0.aarch64" Signed-off-by: Zheng Ruoqin <zhengrq.fnst@cn.fujitsu.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21libnl: add ptest supportYi Fan Yu
All tests are installed, but only what `make check` runs is run, so currently that's 1 test named `check-all` `libcheck` needs to be present for ./configure to generate the check* tests. An issue asking about upstream testing strategy is opened at https://github.com/thom311/libnl/issues/270 Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21selftest/incompatible_lic: Update the tests after the 'or-later' license ↵Richard Purdie
handling changes With the separate of the "-only" and "-or-later" licenses, we need to update the tests to match the messages now given in the output. Also use a mix of canonicalised and non-canonlised names in the reference recipes to help test those cases and ensure coverage. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-02-21license_image: Don't canonicalise INCOMPATIBLE_LICENSERichard Purdie
The code internally correctly handles canonicalisation of these license fields, we shouldn't call it manually. The issue is that the fields can contain wildcards and GPLv3* means something quite different to GPLv3-only*. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-20 05:23:29 +0000