summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2021-11-25rootfs_rpm.bbclass: distutils -> sysconfig moduletimo/core-deprecate-distutils_14610Tim Orling
Change a comment to reference our custom changes to the sysconfig module, as dnf no longer uses distutils. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3native.bbclass: distutils -> sysconfigTim Orling
In the comment it says we patch distutils modules, but we now are patching sysconfig and not using disutils. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25lib/oe/terminal.py: use bb.version.LooseVersionTim Orling
distutils has been deprecated in Python 3.10 and is slated for removal in Python 3.12 (~October 2023). Refactor to use the newly imported bb.version.LooseVersion instead of distutils.version.LooseVersion. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3: refactor python-config patchTim Orling
Drop legacy python-config.patch distutils is deprecated in Python 3.10 and will be removed in Python 3.12 (~October 2023). Rather than wholesale import the distutils.sysconfig module, refactor to replicate legacy distutils usage that we need. This merges changes to get_python_inc from 12-distutils-prefix-is-inside-staging-area.patch [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25dnf: drop python3-disutils dependencyTim Orling
Upstream dropped the now deprecated distutils: 18995d65 Remove distutils which are deprecated in python3.10 (RhBug:1950229) Usage was replaced with sysconfig, which is in pyton3-core [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25waf.bbclass: drop usage of distutilsTim Orling
Refactor to use newly imported bb.version.LooseVersion [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25recipetool/create_buildsys_python.py: less distutilsTim Orling
distutils is deprecated in Python 3.10 with removal in Python 3.12 (~October 2023). Replace distutils.command.build_py with setuptools.command.build_py. There is still a check which decides to inherit setuptools3 vs distutils3 that will need to be refactored when we add pyproject.toml and setup.cfg support for more modern PEP 517 packages. Once distutils3.bbclass is dropped, any recipe inheriting distutils3 will throw a parsing error. The plan is to move distutils*.bbclasses to meta-python. However if meta-python is not in bblayers, the parsing error would still occur. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25gstreamer1.0-python: inherit setuptools3-baseTim Orling
Drop distutils3-base usage as it is now deprecated. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25sanity.bbclass: drop usage of distutilsTim Orling
Refactor to use newly imported bb.version.LooseVersion and replace `import distutils.sysconfig` with 'import sysconfig`. https://www.python.org/dev/peps/pep-0632/#id23 [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3-setuptools: do not depend on distutilsTim Orling
No longer depend on python3-distutils, current versions of setuptools vendor as _distutils. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25bind: inherit setuptools3-base instead of distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3-pygobject: setuptools instead of distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25scripts/buildhistory-diff: drop use of distutilsTim Orling
The use of distutils.version.LooseVersion to check for GitPython > 0.3.1 is not really needed anymore since any supported distribution has at least 1.0.0 (centos-7 via epel7, debian-9, ubuntu-16.04) If we want to reinstate this check, alternatives would be to require python3-packaging on all hosts and use packaging.version.Version or use an imported LooseVersion in bb.version. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25btrfs-tools: use setuptools3-base not distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25librepo: inherit setuptools3-base not distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25createrepo-c: inherit setuptools3-base not distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25libcomps: inherit setuptools3-base not distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25systemtap: use setuptools-base not distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3-pip: inherit setuptools3 not distutils3Tim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25gpgme: inherit setuptools-base not distutilsTim Orling
What was distutils-common-base has been merged into setuptools3-base, since we no longer need to support python2 and python3. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3-dbus: inherit setuptools3-base not distuilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25libdnf: inherit setuptoools3-base not distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25dnf: inherit setuptools3-base instead of distutilsTim Orling
[YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25python3-cython: DISTUTILS_* -> SETUPTOOLS_*Tim Orling
Refactor to new SETUPTOOLS_* variables [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25setuptools: refactor for no distutils bbclassesTim Orling
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25classes/distutils-*: add warning of deprecationTim Orling
distutils has been deprecated in Python 3.10 and will be removed in Python 3.12 (predicted release date October 2023). Add a warning now that recommends using the roughly equivalent setuptools-* classes. [YOCTO #14610] Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
2021-11-25gcc: Drop no longer needed patchRichard Purdie
This patch was mentioned upstream a long time ago: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47256 Changes from gcc 10 onward mean it is no longer needed as mentioned in the above bug report. Drop the patch. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25meta-skeleton: fix warnings for append operators combined with +=Yi Zhao
Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25oe/utils: by default cap cpu_count() to 64 coresRoss Burton
Larger systems may have large numbers of cores, but beyond a certain point they can't all be used for compiling: whilst purely compute-intensive jobs can be parallelised to hundreds of cores, operations such as compressing (needs lots of RAM) or compiling (lots of I/O) don't scale linearly. For example, the Marvel ThunderX2 has 32 cores, each capable of executing four threads, and can be configured with two sockets, making 256 CPUs according to Linux. Zstd using 256 threads has been seen to fail to allocate memory during even small recipes such as iso-codes. Add a default cap of 64 CPUs to the cpu_count() method so that extreme parallisation is limited. 64 is high enough that meaningful gains beyond it are unlikely, but high enough that most systems won't be effected. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25sstate: explicitly name the checkhashes thread poolRoss Burton
Give this thread pool a name for clarity. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25oe/utils: allow naming threads in ThreadedPoolRoss Burton
When looking at logs involving thread pools it is useful if the threads can be named. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25python3-setuptools: update 58.5.3 -> 59.2.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25python3-packaging: update 21.2 -> 21.3Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25bind: update 9.16.22 -> 9.16.23Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25vulkan: update 1.2.191.0 -> 1.2.198.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25systemd: update 249.6 -> 249.7Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25cmake: update 3.21.4 -> 3.22.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25git: update 2.33.1 -> 2.34.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25gptfdisk: submit patch upstreamAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25weston: mark patch as deniedAlexander Kanavin
upstream has explained in the patch submisstion how the issue should be solved differently; we should work towards that. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25elfutils: submit patch upstreamAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25elfutils: update 0.185 -> 0.186Alexander Kanavin
Drop glibc-2.34-fix.patch merged upstream. Rework support for error() on non-glibc targets: upstream now provides its own implementation, so we can drop the patch that adds ours; said implementation isn't build-tested with tests, so ptest has to be disabled on musl. This, in turns, allows dropping 0004-Fix-error-on-musl.patch. License-Update: copyright years Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25dpkg: replace a patch with a tweak to an already existing sed fixupAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25diffstat: remove unneeded patchAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25apt: drop unneeded chunk from a musl patch, submit the rest upstreamAlexander Kanavin
Upstream has inserted guards around the use of offending constant. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25ell: remove unneeded patchAlexander Kanavin
Upstream added internal implementation shortly after the patch was added. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-25glib-2.0: submit patch upstreamAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-24logrotate: add a link to upstream review for one of the patchAlexander Kanavin
The patch author (Robert Yang) has been asked by email to rework the patch. Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-24groff: include references to corresponding upstream commits in a patchAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex@linutronix.de> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-11-24kernel-yocto: conditionally enable stack protection checking on x86-64Bruce Ashfield
The kernel Makfile uses pkgconfig to check for libelf when enabling CONFIG_STACK_VALIDATION. We already have libelf in our DEPENDS, but the kernel Makefiles hardcode 'pkgconfig', so fail to pick up our pkgconfig-native binary that would report the correct flags and paths for libelf support. Rather than patching the kernel Makefile's to use pkgconfig-native, we can use the KERNEL_EXTRA_ARGS variable to pass the definition of HOST_LIBELF_LIBS via the kernel build commmand line. We conditionally set HOST_LIBELF_LIBS based on "stack" being in a newly introduced variable KERNEL_DEBUG_OPTIONS. The value of HOST_LIBELF_LIBS is the same as pkgconfig-native would set in a kernel build (but we cannot call pkgconfig at the point this variable is set). Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-04-23 18:24:10 +0000