summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools
AgeCommit message (Collapse)Author
2021-08-26rust: Avoid buildtools+uninative issues with glibc symbols mismatchesRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust: Skip target recipe since it doesn't workRichard Purdie
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. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust-llvm: Add missing HOMEPAGERichard Purdie
Add a missing HOMEPAGE entry to the recipe (fixing a selftest failure). Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust-native: Avoid stripped warningRichard Purdie
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! Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26cargo: Ensure cargo-cross-canadian doesn't have native/nativesdk versionsRichard Purdie
native/nativesdk variants of a cross-canadian recipe don't make any sense so avoid these recipe variants. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust-cross-canadian-common: Use rust.inc directly, not rust-targetRichard Purdie
We don't want cross-canadian to see the native BBCLASSEXTEND as that generates a recipe which makes no sense. Avoid this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust-cross*: Fix OVERRRIDE references in task signature computationRichard Purdie
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 Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust: remove Rust version 1.51.0 toolchainRandy MacLeod
We typically only have one version so remove the older rust toolchain. This also fixes a maintainers oe-selftest. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust-common.inc: Fix build failure with qemuppc64.Vinay Kumar
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". 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>
2021-08-26cargo/rust/rustfmt: exclude from worldRandy MacLeod
cargo, rust, and rustfmt can't be built for the targets yet so exclude them from world builds. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust: update the README to conform to being in oe-coreRandy MacLeod
Provide the full link to the meta-rust issue since the README is no longer part of meta-rust. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust: mv README.md to recipes-devtools/rust/README-rust.mdRandy MacLeod
Import the meta-rust/README.md but relocate and rename it. Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26rust: initial merge of most of meta-rustRandy MacLeod
In the meta-rust repo at commit: 448047c Upgrade to 1.54.0 (#359) Make the required directories: mkdir ../oe-core/meta/recipes-devtools/rust mkdir ../oe-core/meta/recipes-devtools/cargo mkdir ../oe-core/meta/recipes-example and then: cp recipes-devtools/rust/* ../oe-core/meta/recipes-devtools/rust cp recipes-devtools/cargo/* ../oe-core/meta/recipes-devtools/cargo cp lib/crate.py ../oe-core/meta/lib cp recipes-example/* ../oe-core/meta/recipes-example cp conf/distro/include/rust_* ../oe-core/meta/conf/distro/include/ cp classes/* ../oe-core/meta/classes/ cp recipes-core/packagegroups/packagegroup-rust-cross-canadian.bb ../oe-core/meta/recipes-core/packagegroups Signed-off-by: Randy MacLeod <Randy.MacLeod@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26vala: upgrade 0.52.4 -> 0.52.5Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26python3-mako: upgrade 1.1.4 -> 1.1.5Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26git: upgrade 2.32.0 -> 2.33.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26ccache: upgrade 4.3 -> 4.4Alexander Kanavin
License-Update: formatting Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-26binutils: drop target flex/bison from build dependenciesAlexander Kanavin
This lengthens dependency chains unnecessarily; also -native versions are already included in DEPENDS via binutils.inc: DEPENDS = "flex-native bison-native zlib-native gnu-config-native autoconf-native" I have also checked that nothing in binutils needs anything from target sysroots of flex/bison: https://lists.openembedded.org/g/openembedded-core/message/155131 Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-25pseudo: Fix to work with glibc 2.34 systemsRichard Purdie
The merge of libdl into libc in glibc 2.34 causes problems for pseudo. Add a fix that works around this issue. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23squashfs-tools: upgrade 4.4 -> 4.5Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23python3-setuptools: upgrade 57.1.0 -> 57.4.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23python3-pygments: upgrade 2.9.0 -> 2.10.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23python3-pip: upgrade 21.2.1 -> 21.2.4Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23python3-git: upgrade 3.1.18 -> 3.1.20Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23pkgconf: upgrade 1.7.4 -> 1.8.0Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23patchelf: upgrade 0.12 -> 0.13Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23mtools: upgrade 4.0.34 -> 4.0.35Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23log4cplus: upgrade 2.0.6 -> 2.0.7Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23libedit: upgrade 20210522-3.1 -> 20210714-3.1Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23help2man: upgrade 1.48.3 -> 1.48.4Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23e2fsprogs: upgrade 1.46.2 -> 1.46.4Alexander Kanavin
Drop big-inodes-for-small-fs.patch: upstream made the same fix. Drop 0001-lib-ext2fs-unix_io.c-do-unlock-on-error.patch 0001-lib-ext2fs-unix_io.c-revert-parts-of-libext2fs-fix-p.patch (upstream has fixed the issue). Add 0001-lib-ext2fs-unix_io.c-revert-parts-of-libext2fs-fix-p.patch to correct a ptest failure due to incorrectly expected inode size (recent change that wasn't run against the tests upstream?). Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23btrfs-tools: update 5.13 -> 5.13.1Alexander Kanavin
Drop patch as issue fixed upstream. Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23python3-numpy: upgrade 1.21.0 -> 1.21.2Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23python3-cython: upgrade 0.29.23 -> 0.29.24Alexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-23tcf-agent: fetching over git:// no longer worksAlexander Kanavin
Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-22python3-hypothesis: enable ptestTim Orling
The upstream "fast" tests (tests/cover and tests/pytest) take over 5 minutes to run and do not run cleanly. They also add dependency on python3-pexpect and python3-ptyprocess (currently in meta-python). The tests are also not included in the pypi tarball, so it would require use of git fetcher and other invasive changes to the recipe, including dropping the pypi inherit. Instead, use two test suites from examples/ References: https://github.com/HypothesisWorks/hypothesis/tree/master/hypothesis-python/tests https://github.com/HypothesisWorks/hypothesis/tree/master/hypothesis-python/examples Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-22python3-hypothesis: upgrade 6.14.8 -> 6.15.0Tim Orling
6.15.0 - 2021-08-22 This release emits a more useful error message when @given() is applied to a coroutine function, i.e. one defined using async def (issue #3054). This was previously only handled by the generic return_value health check, which doesn’t direct you to use either a custom executor or a library such as pytest-trio or pytest-asyncio to handle it for you. 6.14.9 - 2021-08-20 This patch fixes a regression in Hypothesis 6.14.8, where from_type() failed to resolve types which inherit from multiple parametrised generic types, affecting the returns package (issue #3060). References: https://github.com/HypothesisWorks/hypothesis/issues/3054 https://github.com/HypothesisWorks/hypothesis/issues/3060 Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-22gcc: also relocate the musl loaderRoss Burton
Alongside GLIBC and UCLIBC, also relocate the musl loader. Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-22gcc: Fix nativesdk builds and multilib fixes with gcc 11Richard Purdie
In newer gcc versions the headers changed locations and our multiconfig and nativesdk tweaks to loader paths wasn't working. The broke buildtools-extended-tarball, particularly on arm. Update to fix this. Ultimately we should dump the gcc specs and check for hardcoded paths. This isn't possible quite yet as this patch doesn't fix the musl ones as we don't use that in mutlilib or nativesdk scenarios at present. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-20python3-hypothesis: upgrade 6.14.5 -> 6.14.8Tim Orling
6.14.8 - 2021-08-16 This patch ensures that registering a strategy for a subclass of a parametrised generic type such as class Lines(Sequence[str]): will not “leak” into unrelated strategies such as st.from_type(Sequence[int]) (issue #2951). Unfortunately this fix requires PEP 560, meaning Python 3.7 or later. 6.14.7 - 2021-08-14 This patch fixes issue #3050, where attrs classes could cause an internal error in the ghostwriter. 6.14.6 - 2021-08-07 This patch improves the error message for issue #3016, where PEP 585 builtin generics with self-referential forward-reference strings cannot be resolved to a strategy by from_type(). References: https://github.com/HypothesisWorks/hypothesis/issues/2951 https://www.python.org/dev/peps/pep-0560 https://github.com/HypothesisWorks/hypothesis/issues/3050 https://www.python.org/dev/peps/pep-0585 Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-20python3-importlib-metadata: upgrade 4.6.3 -> 4.6.4Tim Orling
v4.6.4 Issue 334: Correct SimplePath protocol to match pathlib protocol for __truediv__. References: https://github.com/python/importlib_metadata/issues/334 Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-20elfutils: Fix ptest dependenciesRichard Purdie
The elfutils ptests require debug symbols for the libc to be available, else we see failures such as those on the autobuilder for the fast ptest image on arm (the dbg symbols are pulled in by other recipes in other images). Also fix various test skips/error messages due to missing gcc/ld and development headers. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-18binutils: Apply upstream patch to fix 'too many open files' on qtwebengineAndreas Müller
Since upgrade of binutils to 2.37 builds of qtwebengine failed to link even with ulimits -n 1000000 (!!). Fix that by applying a patch from stable 'binutils-2_37-branch'. Signed-off-by: Andreas Müller <schnitzeltony@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-18qemu: fix CVE-2021-3682Sakib Sajal
Signed-off-by: Sakib Sajal <sakib.sajal@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-17prelink: add PACKAGECONFIG for selinuxYi Zhao
Add PACKAGECONFIG for selinux rather than disable it directly. This is useful for selinux distro feature. Signed-off-by: Yi Zhao <yi.zhao@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-17elfutils: Add zstd PACKAGECONFIG for determinismRichard Purdie
Ensure builds as deterministic by covering all compression configuration options. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-13perl: do_create_rdepends_inc override syntaxTim Orling
The do_create_rdepends_inc function is used to recreate the perl-rdepends.txt file. Update RDEPENDS_ to RDEPENDS: for the new override syntax. Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-12python3-scons{-native}: upgrade 4.1.0 -> 4.2.0Tim Orling
Update patch as setup.cfg changes are now in upstream. License-Update: Update Copyright years NOTE: The 4.2.0 Release of SCons will deprecate Python 3.5 Support. Python 3.5 support will be dropped in the next major release. RELEASE 4.2.0 - Sat, 31 Jul 2021 18:12:46 -0700 From Byron Platt: - Fix Install() issue when copytree recursion gives bad arguments that can lead to install side-effects including keeping dangling symlinks and silently failing to copy directories (and their subdirectories) when the directory already exists in the target. From Joseph Brill: - Internal MSVS update: Remove unnecessary calls to find all installed versions of msvc when constructing the installed visual studios list. From William Deegan: - Improve Subst()'s logic to check for proper callable function or class's argument list. It will now allow callables with expected args, and any extra args as long as they have default arguments. Additionally functions with no defaults for extra arguments as long as they are set using functools.partial to create a new callable which set them. - Fix Issue #3035 - mingw with SHLIBVERSION set fails with either not a dll error or "Multiple ways to build the same target were specified for:". Now mingw will disable creating the symlinks (and adding version string to ) dlls. It sets SHLIBNOVERSIONSYMLINKS, IMPLIBNOVERSIONSYMLINKS and LDMODULENOVERSIONSYMLINKS to True. - Added --experimental flag, to enable various experimental features/tools. You can specify 'all', 'none', or any combination of available experimental features. - Fix Issue #3933 - Remove unguarded print of debug information in SharedLibrary logic when SHLIBVERSION is specified. - Fix versioned shared library naming for MacOS platform. (Previously was libxyz.dylib.1.2.3, has been fixed to libxyz.1.2.3.dylib. Additionally the sonamed symlink had the same issue, that is now resolved as well) - Add experimental ninja builder. (Contributed by MongoDB, Daniel Moody and many others). - Fix #3955 - _LIBDIRFLAGS leaving $( and $) in *COMSTR output. Added affect_signature flag to _concat function. If set to False, it will prepend and append $( and $). That way the various Environment variables can use that rather than "$( _concat(...)$)". - Fix issue with exparimental ninja tool which would fail on windows or when ninja package wasn't installed but --experimental=ninja was specified. - As part of experimental ninja tool, allow SetOption() to set both disable_execute_ninja and disable_ninja. From David H: - Fix Issue #3906 - `IMPLICIT_COMMAND_DEPENDENCIES` was not properly disabled when set to any string value (For example ['none','false', 'no','off']) Also previously 'All' wouldn't have the desired affect. From Ivan Kravets: - Provide a custom argument escape function for `TempFileMunge` using a new `TEMPFILEARGESCFUNC` variable. Useful if you need to apply extra operations on a command argument before writing to a temporary file (fix Windows slashes, normalize paths, etc.) From Henrik Maier: - DocbookXslt tool: The XSLT stylesheet file is now initialized to an env.File() Node, such that dependencies work correctly in hierarchical builds (eg when using DocbookXslt in SConscript('subdir/SConscript') context. From Daniel Moody: - Update CacheDir to use uuid for tmpfile uniqueness instead of pid. This fixes cases for shared cache where two systems write to the same cache tmpfile at the same time because the happened to get the same pid. - Added support for passing custom CacheDir derived classes to SCons. Moved copy_from_cache attribute from the Environment class to CacheDir class. Code contributed by MongoDB. - Update BuildTask to pass all targets to the progress object fixing an issue where multi-target build nodes only got the first target passed to the progress object. - Fix a potential race condition in shared cache environments where the permissions are not writeable for a moment after the file has been renamed and other builds (users) will copy it out of the cache. Small reorganization of logic to copy files from cachedir. Moved CacheDir writeable permission code for copy to cache behind the atomic rename operation. - Added marking of intermediate and and multi target nodes generated from SConf tests so that is_conftest() is more accurate. - Added test for configure check failing to ensure it didn't break generating and running ninja. From Mats Wichmann: - Initial support in tests for Python 3.10 - expected bytecode and one changed expected exception message. Change some more regexes to be specified as rawstrings in response to DeprecationWarnings. - Add an example of adding an emitter to User Guide (concept from Jeremy Elson) - Add timing information for sconsign database dump when --debug=time is selected. Also switch to generally using time.perf_counter, which is the Python recommended way for timing short durations. - Drop remaining definitions of dict-like has_key methods, since Python 3 doesn't have a dictionary has_key (maintenance) - Do not treat --site-dir=DIR and --no-site-dir as distinct options. Allows a later instance to override an earlier one. - Ignore empty cmdline arguments when computing targets (issue 2986) - Remove long-deprecated construction variables PDFCOM, WIN32_INSERT_DEF, WIN32DEFPREFIX, WIN32DEFSUFFIX, WIN32EXPPREFIX, WIN32EXPSUFFIX. All have been replaced by other names since at least 1.0. - Add a __iadd__ method to the CLVar class so that inplace adds (+=) also work as expected (issue 2399) - Remove local copy of CLVar in EnvironmentTests unittest file - should be testing against the production version, and they didn't really differ. - Don't strip spaces in INSTALLSTR by using raw subst (issue 2018) - Deprecate Python 3.5 as a supported version. - CPPDEFINES now expands construction variable references (issue 2363) - Restore behavior that Install()'d files are writable (issue 3927) - Simplified Mkdir(), the internal mkdir_func no longer needs to handle existing directories, it can now pass exist_ok=True to os.makedirs(). - Avoid WhereIs exception if user set a tool name to empty (from issue 1742) - Maintenance: remove obsolete __getslice__ definitions (Py3 never calls); add Node.fs.scandir to call new (Py3.5) os.scandir; Node.fs.makedirs now passes the exist_ok flag; Cachedir creation now uses this flag. - Maintenance: remove unneeded imports and reorganize some. Fix uses of warnings in some tools which instantiated the class but did nothing with them, need to instead call SCons.Warnings.warn with the warn class. - Drop overridden changed_since_last_build method in Value class. - Resync the SetOption implementation and the manpage, making sure new options are available and adding a notes column for misc information. SetOption equivalents to --hash-chunksize, --implicit-deps-unchanged and --implicit-deps-changed are enabled. - Add tests for SetOption failing on disallowed options and value types. - Maintenance: eliminate lots of checker complaints about Util.py. - Maintenance: fix checker-spotted issues in Environment (apply_tools) and EnvironmentTests (asserts comparing with self). For consistency, env.Tool() now returns a tool object the same way Tool() has done. - Change SConscript() missing SConscript behavior - if must_exist=False, the warning is suppressed. - Make sure TEMPFILEPREFIX can be set to an empty string (issue 3964) From Dillan Mills: - Add support for the (TARGET,SOURCE,TARGETS,SOURCES,CHANGED_TARGETS,CHANGED_SOURCES}.relpath property. This will provide a path relative to the top of the build tree (where the SConstruct is located) Fixes #396 From Andrew Morrow: - Fix issue #3790: Generators in CPPDEFINES now have access to populated source and target lists Signed-off-by: Tim Orling <timothy.t.orling@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-12e2fsprogs: ensure small images have 256-byte inodesRoss Burton
e2fsprogs calls filesystems larger than 3MB but smaller than 512MB "small", which has some implications: - blocksize 1024 instead of 4096 - inode_ratio 4096 instead of 16384 - inode_size 128 instead of 256 The outcome of the inode size dropping to 128 bytes is that they cannot store 64-bit timestamps, so are not Y2038-safe. A previous attempt to solve this problem[1] changed some of the canned wic files to pass -T default to mkfs.ext4, but this only covered wic images and not traditional images. Also, actually small filesystems, for example a core-image-minimal, will happily be tens of megabytes and with the "default" options will result in an image which runs out of blocks before it runs out of space: mkfs.ext4: Could not allocate block in ext2 filesystem while populating file system Considering that many OpenEmbedded images are in fact "small", being 2038-safe is worth the marginal increase is disk usage. This patch alters the small configuration in native builds so that it also has 256-byte inodes. Target is unchanged so that standard behaviour is maintained outside of the build. This is actually the same underlying patch that Mathieu Dubois-Briand sent in April, but the wic change in [1] was accepted instead. I believe that is the wrong approach and this approach covers more cases. [ YOCTO #14478 ] [1] openembedded-core eecbe62 [2] https://lists.openembedded.org/g/openembedded-core/message/150298 Signed-off-by: Ross Burton <ross.burton@arm.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2021-08-12meta: use new override syntax in commentsChen Qi
Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-14 23:53:48 +0000