- Some distributions with UTF-8 locale have problem when National Language
Support is enabled. Add there an option to disable it.
(From OE-Core rev: da630d6d81a396c3e1635fbd7b8103df47ed2732)
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is done when starting up qemu has failed, but is not done
when qemu started ok, but fails later in QMP communication.
Output from runqemu does contain valuable information to find out
why, so rather than fix all the QMP fails to include it, let's just
print it in stop().
(From OE-Core rev: 6e2bf68e4401db747484c2c8ba0f77500b1d2d49)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Setting the Meson buildtype to "debug" will by default only enable the
-g option to the compiler, which should not matter for OE-Core as it is
already enabled by setting DEBUG_BUILD to 1 in the first place. However,
if the package uses get_option('debug') in its meson.build files to
enable package specific debug code, this will now trigger as intended.
(From OE-Core rev: 7c7c353858a020153be5dba78480b91a28c7a05b)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When CONFIG_TRACEPOINTS is not enabled in kernel config - module
compilation is skipped, which causes the ${D}/${nonarch_base_libdir} not
to be created.
This fails later in do_install:append() due to the fact that find
command in executed for non-existing folder.
Check for folder existence before find command in executed.
(From OE-Core rev: de0aa1700ed4e6f04b0a233eb1f6d2ac598e7ed8)
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If the kernel configuration enables module signing but no key
is provided, then the kernel generates one during the kernel build.
The current runtime-dependency references (with only package names
without full versions) allow mixed package installations from different
rebuilds of the same kernel version.
This creates an issue because then the modules either don't work
or taint the kernel.
Tighten RDEPENDS with the full package version, i.e. use (= ${EXTENDPKGV})
markers for inter-package dependencies.
The kernel will pull in the kernel-modules subpackage of the same
exact version automatically if KERNEL_SPLIT_MODULES="0" is set.
Otherwise the situation is the same as with the old default with
one subpackage per kernel module where they have to be upgraded
manually.
(From OE-Core rev: 56428d15803733e14d6f1faf5f77eb933ef966f3)
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
For some use cases, a monolithic kernel-modules package containing
all modules built from the kernel sources may be preferred.
For one, download time is shorter and installation time is faster.
Set KERNEL_SPLIT_MODULES="0" for this in. The default is one subpackage
per module.
Also, adapt kernel.bbclass to KERNEL_SPLIT_MODULES != "1" case
Extra RDEPENDS and other inter-package references are needed in
this case.
(From OE-Core rev: 4b13409d82e9d576e32b978f7a42a143127ab894)
Signed-off-by: Zoltán Böszörményi <zboszor@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
- update to next stable version 1.34.0
- refresh defconfig
- remove and refresh already merged patches
(From OE-Core rev: d0e694ef4ec7bd862bdefee494210e3878152b44)
Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When pam is enabled, it complains installed-vs-shipped QA issue:
| ERROR: libcgroup-2.0-r0 do_package: QA Issue: libcgroup:
Files/directories were installed but not shipped in any package:
| /lib/security/pam_cgroup.a
(From OE-Core rev: 21eccd79bdaa93b407da9cf0902d57fd225141ee)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since commit [df313aa810 pseudo: Fix to work with glibc 2.34
systems] applied, it fixed native only. And nativesdk has
the similar issue
Tweak library search order, make prebuilt lib ahead of recipe lib,
after apply the fix:
...
$ readelf -a lib/pseudo/lib64/libpseudo.so | grep 'Shared library'
0x0000000000000001 (NEEDED) Shared library: [libdl.so.2]
0x0000000000000001 (NEEDED) Shared library:[libpthread.so.0]
0x0000000000000001 (NEEDED) Shared library: [libc.so.6]
...
(From OE-Core rev: d6d116b5db78645958ea30be3d0572e0f6d7bd92)
Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fixes ptest failures in python3-jinja2.
Backport patch from upstream, for now.
Modify upstream patch to use toml and not tomli.
We will add the new recipe for python3-tomli when
we have an upgrade to python3-pytest.
Remove this when we upgrade pytest to a version containing
the commit: fbba504cd5e1a74d528a41a11a7b82297cd7da74
(From OE-Core rev: b4cfb0b0dab6bc7f43bab04cdf4f16c145be0223)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* All ptests pass on qemux86-64
pluggy 1.0.0 (2021-08-25)
Deprecations and Removals
#116: Remove deprecated implprefix support. Decorate hook
implementations using an instance of HookimplMarker instead.
The deprecation was announced in release 0.7.0.
#120: Remove the deprecated proc argument to call_historic. Use
result_callback instead, which has the same behavior. The
deprecation was announced in release 0.7.0.
#265: Remove the _Result.result property. Use _Result.get_result()
instead. Note that unlike result, get_result() raises the
exception if the hook raised. The deprecation was announced in release
0.6.0.
#267: Remove official support for Python 3.4.
#272: Dropped support for Python 2. Continue to use pluggy 0.13.x
for Python 2 support.
#308: Remove official support for Python 3.5.
#313: The internal pluggy.callers, pluggy.manager and pluggy.hooks
are now explicitly marked private by a _ prefix (e.g.
pluggy._callers). Only API exported by the top-level pluggy module is
considered public.
#59: Remove legacy __multicall__ recursive hook calling system. The
deprecation was announced in release 0.5.0.
Features
#282: When registering a hookimpl which is declared as
hookwrapper=True but whose function is not a generator
function, a PluggyValidationError exception is now raised.
Previously this problem would cause an error only later, when
calling the hook.
In the unlikely case that you have a hookwrapper that returns a
generator instead of yielding directly, for example:
def my_hook_real_implementation(arg):
print("before")
yield
print("after")
@hookimpl(hookwrapper=True)
def my_hook(arg):
return my_hook_implementation(arg)
change it to use yield from instead:
@hookimpl(hookwrapper=True)
def my_hook(arg):
yield from my_hook_implementation(arg)
#309: Add official support for Python 3.9.
(From OE-Core rev: 4cb9623933e3daeb754c06263167be61100f6c0a)
Signed-off-by: Tim Orling <timothy.t.orling@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
It is probably a good idea if the comment that describes how variable
overrides work use the new override syntax...
(From OE-Core rev: 1fd8882db9011a6fe18da7611fba3426fd5cb00d)
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rust-llvm-liblto and rust-llvm-staticdev sometimes vary in contents. Exclude
them from the test for now until we can work on and resolve the issues.
(From OE-Core rev: 60c12da5aae2534c972df851f26e4523fed03afc)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The -cc wrapper can be used for linking and can fail if key flags are missing:
| error: linking with `[path]/tmp/work/x86_64-linux/rust-native/1.54.0-r0/wrapper/target-rust-cc`
Add the flags to fix builds even if that is counter-intuitive (cc would
normally be used for compiling and ccld for linking).
(From OE-Core rev: 62242e83c49b81a9ea65c9a1f5957a7c309d910a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
If we use an external buildtools tarball, that combined with uninative results
in build failures with symbol mismatches. This was tracked down to the prebuilt
rust binaries that are downloaded. The libc/loader used to load them is used to
execute target binaries/libraries and therefore anything with built with a newer
libc would fail.
Add code to use patchelf to change the interpreter to our own uninative one if
present which ensures the newer libc and loader are used, hence avoiding the issue.
(From OE-Core rev: 099c761ffddcc828329d3083cc8f3d24b43e9277)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Since the target rust recipe is skipped but the native variant is not,
this confuses the test. Add rust to the list of special cases to avoid
test failures as the current code can't handle the skip.
(From OE-Core rev: 842cba1820416d79e30e3f1940e2486707fc7cff)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The target rust recipe is known not to work. Add a SkipRecipe entry for
that so world builds don't include something known to be broken and
hence give users a sensible message if they do try and build it rather
than a build failure.
(From OE-Core rev: 16c77c82ff6635b0180690ea117e2eff8fd63afb)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a missing HOMEPAGE entry to the recipe (fixing a selftest failure).
(From OE-Core rev: 71782d90cff825bd9c20d49590245565a6194bf8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Instead of giving the following warning, hide it since we don't plan to change it.
WARNING: rust-native-1.54.0-r0 do_populate_sysroot: File '/media/build1/poky/build/tmp/work/x86_64-linux/rust-native/1.54.0-r0/recipe-sysroot-native/usr/lib/rustlib/x86_64-linux/bin/rust-llvm-dwp' from rust-native was already stripped, this will prevent future debugging!
(From OE-Core rev: ec5f0c77882ccbd5797519f5ded4e528eb687008)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
native/nativesdk variants of a cross-canadian recipe don't make any
sense so avoid these recipe variants.
(From OE-Core rev: 4ba7fb0b6a5021bca73aade4af390e8e017b491a)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We don't want cross-canadian to see the native BBCLASSEXTEND as that
generates a recipe which makes no sense. Avoid this.
(From OE-Core rev: f3648d18c4e05f38053bb1fd73796a6e05d61928)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The oeqa selftest test:
sstatetests.SStateTests.test_sstate_sametune_samesigs
which checks if the sstate checksums of two identical machines
(using the same tune) are the same, apart from changes within
the machine specific stamps directory, fails on the assertion:
self.assertCountEqual(files1, files2)
due to the signature of various 32 bit package builds such as:
x86_64-linux/lib32-rust-cross-i686
x86_64-linux/rust-cross-i686
x86-pokymllib32-linux/lib32-libstd-rs
x86-pokymllib32-linux/lib32-rust
differing. Jumping down the rabbit hole past all the bitbake-diffsig
outputs that differ due to dependent hashes, you come to a diff of:
-Variable MACHINEOVERRIDES value is ${@bb.utils.contains('TUNE_FEATURES', 'mx32', 'x86-x32:', '', d)}${@bb.utils.contains('TUNE_FEATURES', 'm32', 'x86:', '', d)}qemuall:${MACHINE}
+Variable MACHINEOVERRIDES value is ${@bb.utils.contains('TUNE_FEATURES', 'mx32', 'x86-x32:', '', d)}${@bb.utils.contains('TUNE_FEATURES', 'm32', 'x86:', '', d)}qemuall:${MACHINE}:qemux86
in
stamps/x86_64-linux/rust-cross-i686/1.54.0-r0.do_rust_gen_target.<sig>
This is because there are two rust functions referencing OVERRIDES
related variables (target_is_armv7 and llvm_features_from_tune). These
indirectly influnce the build and should be excluded from the signatures
directly as is done in other toolchain recipes, e.g.:
39bfa0dd32 recipes/*-cross recipes: ignore TARGET_ARCH sstate hash
(From OE-Core rev: 72d67410e92207a98a801ddf0cb9f1297a752975)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
We typically only have one version so remove the older
rust toolchain. This also fixes a maintainers oe-selftest.
(From OE-Core rev: d8ff9672d2686801d535a91fa28a92e38d8f0409)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Fix the test_sstate_noop_samesigs oe-selftest that
produces an error like:
core2-64-poky-linux/libstd-rs/1.54.0-r0.do_configure.sigdata differs:
basehash changed from <hash-a> to <hash-b>
Variable http_proxy value changed from '' to 'http://example.com/'
by simply removing the proxy config option. This may be added back
after merge to oe-core if needed and if the diffsigs check passes.
(From OE-Core rev: 81ad8aceaacda726361e953778294de20eeac24e)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The glibc build of "rust-hello-world" throws error in libstd-rs package.
error: unrecognized arch "powerpc64le" in target specification
The same got fixed by changing the arch to "powerpc64".
(From OE-Core rev: 1a28dd447c248f6b7f0efd121160ac798e2abf0c)
Signed-off-by: Vinay Kumar <vinay.m.engg@gmail.com>
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
I'm willing to do the rust package maintenance but
if anyone else wants to sign up, that would be welcome.
(From OE-Core rev: 531d86cf1e11b034e23d1b682e475c1dde7b1a20)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
cargo, rust, and rustfmt can't be built for the targets yet
so exclude them from world builds.
(From OE-Core rev: 3ade1015b5bbd6aac9dd9974a6a5712958a5f5ed)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Provide the full link to the meta-rust issue since
the README is no longer part of meta-rust.
(From OE-Core rev: 11cb8e67f356d4758c3aae0e5851a44256459e77)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Import the meta-rust/README.md but relocate and rename it.
(From OE-Core rev: a36b43187f9b78c279bdbd0ee9c6f7063a0e7cc7)
Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Upstream has converted from gtk-doc to gi-docgen.
(From OE-Core rev: 7fc1ca1edc9ab6eca7a57588397607b86beb3f07)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Drop merged 0001-correctly-use-3-parameters-for-close_range.patch
(From OE-Core rev: 592335a75dbf28d2e3c5f0c62ad96d38420ae1f9)
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
