Instead of reusing a "target_section" variable, name them host and build
section instead. This patch sets things up for other improvementsm,
separating out the renaming.
(From OE-Core rev: 279b809e8306b0eb6ae6caeb6b0a3c3c62d2f9d2)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The code was using a mixture of XXX_SYS and RUST_XXX_SYS. Use
RUST_XXX_SYS consistently and add the variables to the global exclsion
on signatures as they're reflected in the directory triplets and trying
to filter them out the hashes separately is too painful.
(From OE-Core rev: ee0c0fdf9c1eba9eece6ed1293fda25bf18964b3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add a patch which removes the sections of code which encode buildpaths. Whilst
not ideal, the patches at least show where the problematic data is coming from
and should allow more focused work to resovle it by someone who has a better
understanding of rust and what this code is doing. It does look unlikely we
actually need this code in our usecases anyway.
(From OE-Core rev: c08c522fc29445aef0c64f0dd8df8a3531c04afa)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
reproducible.patch
refreshed for new version.
0001-change-shebang-to-python3.patch
removed as not needed since upstream has removed the shebang lines.
License-Update:
src/pip/_vendor/html5lib/LICENSE: removed since it's not it new version
src/pip/_vendor/chardet/LICENSE: file format modified, change St to Street
src/pip/_vendor/pygments/LICENSE: Copyright year updated to 2022
(From OE-Core rev: d69f360bb48001a4ec9220c8f935bb5fe43b4f7a)
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:
=========
Error out instead of crashing when marshaling unsupported fundamental types in some cases !180
Add a workaround for a PyPy 3.9+ bug when threads are used !200
Fix crashes when marshaling zero terminated arrays for certain item types !191
Fix a crash/refcounting error in case marshaling a hash table fails !191
Make the test suite pass again with PyPy !191
tests: support running tests with (MSVC) CPython 3.8+ on Windows !206
interface: Fix leak when overriding GInterfaceInfo !204
setup.py: look up pycairo headers without importing the module (helps with building on Windows and MSVC CPython 3.8+) !205
(From OE-Core rev: 14c442bfe4886e6180bd58f5e69928efd54e9c3c)
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:
===========
-Fix relative $ref resolution when the base URI is a URN or other scheme (#544).
-pkgutil.resolve_name is now used to retrieve validators provided on the command
line. This function is only available on 3.9+, so 3.7 and 3.8 (which are still
supported) now rely on the pkgutil_resolve_name backport package. Note however
that the CLI itself is due to be deprecated shortly in favor of check-jsonschema.
-best_match no longer traverses into anyOf and oneOf when all of the errors
within them seem equally applicable. This should lead to clearer error messages
in some cases where no branches were matched.
(From OE-Core rev: 203dc71c2b2a712a88f41fc6a5b9894d36d0d3c0)
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>
As discussied in [YOCTO #14717] cmake contains a OEToolchainConfig.cmake
file to configure the toolchain correctly in cross-compile build for recipes
using cmake. The CMAKE_ASM_FLAGS are the configuration are meant for assembly,
but the spelling is incorrect and the Flag is ASFLAGS for gcc and other compilers.
So this variable might neever have worked and it is better for
recipes to specify their own.
(From OE-Core rev: 72729ffbab53f95ee9dd1bc22913d9b864495930)
Signed-off-by: Martin Beeger <martin.beeger@online.de>
Signed-off-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When using meson-native directly from bitbake this has no effect and
everything works as before; the use case is being able to build
meson-driven projects from the 'direct SDK' environment. Build systems
like cmake/autotools are entirely driven by environment variables,
but meson needs configuration files, and so this replicates how SDKs
set things up.
In particular, with this change the libepoxy build test from the SDK
test suite is able to pass.
(From OE-Core rev: 87d4f6d176f27c22dbb99abc271b9a6eaca314f8)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove further code duplication by allowing the main function to be
configurable.
(From OE-Core rev: 2d4b35a0db1220e7a7f1b6776223aa4d40a3f246)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently most of the rust recipes use this code but it is all piecemeal.
Turn the code into a class where things can start to be rationalised. Ultimately
some of the data and python code should be moved to a python library but one step
at a time.
No functionality changes.
(From OE-Core rev: 3795285cbf362e13b8151bfdbe1bce999ac28641)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Some of the subtleties in the different codepaths for target rust json generation
were not easy to spot. Start to simplfy the code to make this clearer.
This patch should not have any functionality change although ABIEXTENSION
has to be excluded from the function signature, the triplet would normally
cover anything set there.
(From OE-Core rev: 0f83d959465e0d99f98ade6803281585931d1b02)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Match the code in rust-cross-canadian so that further simplifications
can be considered in future.
(From OE-Core rev: 5cb62d0a33777cb9afb1eea5f736a2580ce50dc7)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
rust-cross had special handling for armv7 targets but we also need this
for cross-canadian. Merge the code into the main function so everything is
consistent.
Also then fix the arm definition to be arm-eabi since ABI is correctly
being looked up.
(From OE-Core rev: ff3c3dbbd2bf1bb7bb70b55cca203e9eedcf14a8)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Based upon a patch from Otavio Salvador <otavio@ossystems.com.br>,
ensure the target json files are written in the correct order with
the most specific last incase it overwrites earlier files if the prefixes
match.
(From OE-Core rev: 1912c4e9e0ecf9655f3b3a41588b54d7956f5899)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When a 'BUILD' target is requested we shouldn't be looking at TARGET_SYS but
at BUILD_SYS. Due to the way rust mangles triplets, we need the HOST_SYS triplet
to work with existing code - fixing that issue is a separate patch.
Also drop the arch_abi argument, it doens't make any sense to a getVar() call
and was a copy and paste error.
Based on a patch from Otavio Salvador <otavio@ossystems.com.br> but separated out
and tweaked.
Fixes: bd36593ba3 ("rust-common: Drop LLVM_TARGET and simplify")
(From OE-Core rev: d554161a045d12411f288394e253c54aa4c1257c)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
io_uring is enabled or disabled depending on whether liburing is available,
so add a PACKAGECONFIG to make this explicit, disabled by default.
(From OE-Core rev: daee79639c39ac6278855b35e0ddf71e52dd13f8)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* it's not used by any other recipe AFAIK
* meta-python2 has own copy for python-setuptools there in:
meta-python2/recipes-devtools/python/python-setuptools/0001-conditionally-do-not-fetch-code-by-easy_install.patch
(From OE-Core rev: 3a5898861337eb4934360ef6ae448896ec061e26)
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Ignore the rmdir cmd if using usrmerge distro feature since the
intention is to delete /lib or /lib64 but not libdir under /usr and
base_libdir = libdir when usrmerge is enabled in distro
(From OE-Core rev: 3b7f6b0e0f1f16f89cd924aac001b4f661c145ca)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
some standalone targets e.g. riscv64-elf disable shared linking for
baremetal ELF ABI in ld, therefore lets make it a static library
(From OE-Core rev: 3c6219dfcbcbde314648ba8cc54a90b32ea1c952)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This disables tests for runtime system specific functions like fcntl
there is no other change seen
+configure:77372: checking for fcntl
+configure:77372: result: yes
In libsttdc++ configure log outputs.
[YOCTO #14803]
(From OE-Core rev: 586b6239252ecf2711930b60f7f0f617e38ac737)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is a dummy shared object therefore reduce dependencies further by
not requiring the C startup files, we wont use this shared library for
anything useful anyway
(From OE-Core rev: e1c4953f5587621d4911416c2e9350ad0c27b296)
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
And spitted the files for the tests into a -test package
buildhistory:
images/raspberrypi4_64/glibc/core-image-base: IMAGESIZE changed from 208024 to 183660 (-12%)
Changes to images/raspberrypi4_64/glibc/core-image-base (installed-package-names.txt):
python3-pyparsing was removed
python3-pip was removed
python3-setuptools-scm was removed
python3-packaging was removed
python3-typing-extensions was removed
python3-pkg-resources was removed
python3-tomli was removed
python3-setuptools was removed
(From OE-Core rev: d744882251236800412870922b30ddbc70d214e5)
Signed-off-by: Jan Vermaete <jan.vermaete@gmail.com>
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
License-Update:
year updated to 2022
URLs of documentation and repositories changed
URLs of license text changed
List of files covered by the BSD 2-Clause License changed
Changelog:
===========
- Drop support for Python 2.7, 3.5, and 3.6.
- Output changes:
HTML5:
Wrap groups of footnotes in an <aside> for easier styling.
The CSS rule .footnote-list { display: contents; } can be used to restore
the behaviour of custom CSS styles.
- After package installation, the CLI commands python -m docutils and docutils
start the generic command line front end tool.
- Support parsing "Markdown" input with 3rd party parsers myst, pycmark, or recommonmark.
- The default values for the "pep-references", "rfc-base-url", and "python-home"
configuration settings now use the "https:" scheme. The PEP-writer template's
header is updated to fix links and resemble the header of official PEPs.
- Various bugfixes and improvements (see HISTORY).
(From OE-Core rev: 91ffa2d80b959018cb8d531a2ec897dda1b2f691)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Major features since 0.1:
- Implement support for legacy source trees
- Add option to loosen dependency checking
(From OE-Core rev: 5260d81dab757120114e103135dfb4c98443afa3)
Signed-off-by: Ross Burton <ross.burton@arm.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
