This helps in building rsync without autoconf patch, since it will be a
while that the round trip is made, better to apply this patch here until
next release of autoconf.
(From OE-Core rev: 11522b98697befcf13076a90cec4f8ade1fa0645)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Running builds from a previously used directory relies on correctness of
'make clean' or incremental 'make', and sadly perl (or perl-cross) does not have either.
The particularly nasty problem, currently occurring, is that sometimes, when reusing
a previous build, we arrive at a combination of timestamps in the tree,
where make becomes very confused, gets lost in its own rules and enters an infinite loop,
never figuring out what needs to be rebuild in what order. Worse, there is no reliable
trigger for this that was found, and any attempts to 'isolate the issue' haven't produced one.
Let's simply add a clean S/B separation for builds, and always run a build from a reproducible
set of files.
[YOCTO #14902]
(From OE-Core rev: 0919f5ec214594380eb5190b4878eadb30e3a471)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Pull in some minor fixes:
pseudo_util: Silence symlink errors and fix resolution bug
ports/linux: Remove build dependency on libattr
Minor build fixes
pseudo_util: Fix resolving relative paths from "/"
(From OE-Core rev: c57d0c57d00cdef622dab3bf783a10d52f8d9ffb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
crossbeam-utils tries to use the triplet to look up whether the target
supports various forms of atomics. We use TARGET_VENDOR and not "-unknown"
in the target case which means this fails and breaks platforms like mips
and powerpc 32 bit. Add a patch to handle TARGET_VENDOR in this case.
(From OE-Core rev: 5d8c01dfed4c82fcc5d504c728a51fb98a262300)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Latest rust has started using ENOTSUP define, which is not available in
the older libc that current release of compiler is using therefore
backport the needed patch. Eventually when vendored version of libc
bumps to 1.33+ we should not need this patch.
(From OE-Core rev: 097e38f28990229c3f54f4e6cb74ca8be0b806e6)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a wrapper for llvm-config which provides flags from the current envrionment
instead of the values hardcoded into llvm-native at compile time. Inspiration
taken from the wrapper in meta-clang but I had to totally rewrite it as:
* the TARGET_* prefixes weren't in our environment
* meson uses --libs --ldflags XXX which didn't work
(From OE-Core rev: 193ee1973f613b72f7f99660aecf652b07652d18)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changes from 1.9.2 to 1.9.3:
----------------------------
* Fix a bunch of minor code issues pointed out using Clang static analyzer.
* New API: pkgconf_solution_free(), which frees a compiled solution graph.
* Fix behavior when overriding global variables with '--define-variable'.
(From OE-Core rev: a48dc992ebf8e664bde4de61ba937a87fc142533)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Changelog:
==========
New features:
context: Support (NEVRA forms, provides, file provides) including globs in the dnf_context_remove func
Bug fixes:
dnf-context: Disconnect signal handler before dropping file monitor ref
Filter out advisory pkgs with different arch during advisory upgrade, fixes possible problems in dependency resulution
Gracefully handle failure to open repo primary file
Fix listing a repository without cpeid
(From OE-Core rev: 57893d38c2725c07b29d974e184be37b3d265d9b)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
0001-device-utils.c-Use-linux-mount.h-instead-of-sys-moun.patch
removed since it's included in 5.19
Changelog:
==========
* send: support protocol version 2
* fi show: print all missing devices
* device stats: add tabular output
* replace: add alias to device group (device replace)
* check: validate free space tree items
* fixes:
* convert: support large filesystems (block count > 32bit)
* recognize filesystems with verity enabled
* mkfs and DUP could write out of order, fix it for zoned mode
* build:
* optional support for LZO and ZSTD in receive
* compatibility with glibc 2.36 (mount.h)
* add fallbacks for new GCC builtins
* other:
* corrupt-block: target specific items, offsets
* documentation updates, new pages from wiki
* new tests
(From OE-Core rev: 53ead3fb0e51e71207dfd62f43f0ec4304524dcc)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
python3-requests makes use of 'zipfile' module, so we need to add
python3-compression as a dependency, otherwise 'import requests'
errors out.
(From OE-Core rev: 6cfe2ed2234a76a3f9da194097781e8d6ce1353b)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Make unique shell variable names for cargo and rust
setup scripts. This change will make it easier to append to the
scripts in a bbappend file by using the variable for the script.
Before this change it was only possible for the last script as
they shared the same variable name.
(From OE-Core rev: 74307f57ad0b3c538be0add11028e4e6199a7662)
Signed-off-by: Peter Bergin <peter@berginkonsult.se>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This package was broken since it was upgraded to 6.48, because
it started using 'exceptiongroup' since then, which is missing
in any meta layer. On target, when importing hypothesis, we meet
the following error:
Traceback (most recent call last):
File "/usr/lib64/python3.10/site-packages/hypothesis/internal/compat.py", line 18, in <module>
BaseExceptionGroup = BaseExceptionGroup
NameError: name 'BaseExceptionGroup' is not defined. Did you mean: 'BaseException'?
ModuleNotFoundError: No module named 'exceptiongroup'
The related codes as below:
try:
BaseExceptionGroup = BaseExceptionGroup
ExceptionGroup = ExceptionGroup # pragma: no cover
except NameError:
from exceptiongroup import (
BaseExceptionGroup as BaseExceptionGroup,
ExceptionGroup as ExceptionGroup,
)
We can see that it tries to use ExceptionGroup and falls back to
use an import from exceptiongroup module.
Looking at the https://github.com/agronholm/exceptiongroup, it says:
"""
This is a backport of the BaseExceptionGroup and ExceptionGroup classes from Python 3.11.
"""
So instead of adding a new recipe for exception group, it might be
better to revert to a working version and wait for python 3.11 to release.
(From OE-Core rev: 37c5b171d7de25b131e77b80d37f8481308bd6fe)
Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It does not yet compile with clang it comes with __ builtin___snprintf_chk Not Supported
formatted output of built-in functions check is failing with clang
somehow it seems to be compiler limitation. Therefore disable building
this component with clang for now
(From OE-Core rev: 5f4b6afb030fe75247cc2da09cdf0ec5259673df)
(From OE-Core rev: 0b3cff906c469bb9d6dfc7fafe385243d00f1c2b)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
