We regenerate the pycache files and the checksums in the manifest are incorrect.
Remove them to avoid this and ensure reproducibility.
(From OE-Core rev: 3c1e7e50c929436d0007d60e738c8270e7e6c7d9)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This test causes OpenSSL to leak some memory. Until this is resolved in
OpenSSL, mark the test as expected-to-fail.
(From OE-Core rev: b32917b113df6dce0200d35dd1b539279635d524)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
python3-bcrypt and python3-pytz both run in just a few seconds, so add
them to the fast list.
(From OE-Core rev: 555cefec5d554eb610166ff9d0cbf0a620d99632)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The python3-cryptography recipe has a lot of tests and uses a large
amount of memory. It is slow (> 30 seconds).
(From OE-Core rev: ca9fefab2457ee86e24b23d99d3351b0dd9e66ef)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
A PEP 517 build backend implementation developed for Poetry. This project
is intended to be a light weight, fully compliant, self-contained package
allowing PEP 517 compatible build frontends to build Poetry managed projects.
(From OE-Core rev: 49e4541b250be296dc7b148858016ff0aaef9afd)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
poetry.core.masonry.api is one of the common PEP-517 build backends.
(From OE-Core rev: b1d2626a501f33c289ecfc557b998982665f84ae)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add missing HOMEPAGE entries to the two recipes imported from meta-oe to fix
selftest failures.
(From OE-Core rev: 7fefeea0b8a0784052e87768588859c703d47fb5)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Dependency for python3-cryptography ptest.
This recipe needs to be kept in lock-step with the version of
python3-cryptography.
(From OE-Core rev: 1dda3ab39e2a28e05b903d970410587f2b58cdef)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* inherit new setuptools_rust class (which inherits new pyo3 class, which
inherits cargo and python3-dir).
* RDEPENDS on python3-pytest-subtests for ptest
* Copy pyproject.toml for ptest as it defines the pytest.marker(s) needed
* Use 'cargo bitbake' to generate the crate:// SRC_URIs
- Needed some hacks to the Cargo.toml in src/rust/ to make this work (probably
only package.repository was strictly required):
[package]
description = "cryptography includes both high level recipes and low level interfaces to common cryptographic algorithms such as symmetric ciphers, message digests, and key derivation functions."
homepage = "https://github.com/pyca/cryptography"
repository = "https://github.com/pyca/cryptography"
* Add patches to src/rust/Cargo.toml to fix cargo errors including pem version
* Add check-memfree.py to ptest to check for sufficient free memory
(From OE-Core rev: 27bd134c899d00d93806ecb0a62ec3f30b1e6ec6)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
setuptools-rust is a plugin for setuptools to build Rust Python extensions
implemented with PyO3 or rust-cpython.
Compile and distribute Python extensions written in Rust as easily as if
they were written in C.
This class inherits pyo3.bbclass (and therefore cargo.bbclass) and
setuptools3.bbclass to make it easier to build Python modules with Rust
extensions.
Need to call pyo3_do_configure to properly setup the PyO3 environment
for cross-compiling.
Need to call cargo_common_do_configure to setup cargo_home/config so
that the linker properly finds e.g. crti.o and crtbeginS.o
It is strongly recommended to provide crates needed for your recipe
using the crate:// fetcher. This can be helped with the cargo-bitbake
command [1].
If you choose not to use the crate fetcher, bitbake vendoring will not
work with setuptools-rust, as it errors out immediately because it cannot
find pyo3 or some other crate. The (strongly discouraged) workaround for
this is to set:
CARGO_DISABLE_BITBAKE_VENDORING = "1"
[1] https://crates.io/crates/cargo-bitbake
(From OE-Core rev: de3e166cf6f0de4fe0681ddb4b209fb9b8b06811)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
PyO3 provides Rust bindings for Python, including tools for creating native
Python extension modules. Running and interacting with Python code from a
Rust binary is also supported.
This class sets up the cross-compilation environment.
Export PYO3_CROSS, PYO3_CROSS_LIB_DIR, PYO3_CROSS_INCLUDE_DIR and CARGO_BUILD_TARGET
to inform tools like setuptools-rust we are cross-compiling.
Export RUSTFLAGS so cargo can find 'std' and 'core' for target
Dynamically generate PyO3 config file and export PYO3_CONFIG_FILE
absolute path. This is the trick that finally made pyo3 work.
(From OE-Core rev: f3130197ed93fd60b4cad326940b02a5554ed089)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Dependency for python3-cryptography 3.4.x+
Only native rustc is supported at this time in oe-core,
therefore it makes no sense to try to build for target.
(From OE-Core rev: 8eaafc114c196fbab2070bfb600634306deef527)
Signed-off-by: Tim Orling <tim.orling@konsulko.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With the upcoming LTS, it is time we changed the bitbake version so
move to 2.0.
(Bitbake rev: 9a13bf8e20b1841ec99281d45be4c4fc1118438c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
By alphabetical order, to get the same order as in the HTML
output, sorted thanks to the ":sorted:" directive.
(Bitbake rev: 8b97af89316a4407dd07649e8aadd495edd86ee4)
Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
ppc64 historically has used l64 for defining u64 types in kernel
asm/types.h defaults to use l64 by default but kernel uses ll64 now a
days, therefore lets use same int-ll64.h to provide these defines like
other architectures
(From OE-Core rev: 22f8a749fa956c82a0fe39eeb6948bd2068eb63a)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Shadow is happily spamming the host syslog with messages and shouldn't be
which suggests the patch isn't working. Redo it to work at the configure
level which is simpler and hopefully more effective.
(From OE-Core rev: 8f1816862b884f226c0ce7f5c89fd75b6791c007)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
