[pull] master from buildroot:master #336
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
When it was introduced in afdb545 (tools: new tool to filter the output of make), brmake made use of unbuffer, so as to try and ensure that no output would get lost between make printing it, and the logger loop time-stamping it and storing it in the logfile, in case the user would interrup the build (SIGINT, ^C) However, unbuffer is missing in our reference build image (we could have added it, but we missed the occasion to do so every time we updated the reference build image). Furthermore, the rationale for using unbuffer, although reasonable, is not so practical: indeed, when the user hits Crtl-C, this is inherently asynchronous, and they can't expect everything to be entirely cleanly terminated, especially buffering. Using unbuffer is thus slightly superfluous. The timestamps will be slightly off because of buffering, but a build generates so much output that this won't be a problem in practice. Drop use of unbuffer. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
All our documented uses of utils/docker-run, besides running it standalone to get an interactive shell, is to use it as a prefix to the otherwise standard command to run, e.g.: - ./utils/docker-run make foo_defconfig - ./utils/docker-run make menuconfig - ./utils/docker-run make - ./utils/docker-run make check-package Commit 8aad67f (utils/brmake: add option to run in docker) departed from that usual convention, by hiding the call to docker-run inside brmake, conditioned by an environment variable. The only reason is that brmake internally used ubuffer. This is no longer the case, so we can now use brmake together with docker-run in the usual manner. This basically reverts commit 8aad67f, after resolving the conflict due to the removal of unbuffer in te previous commit. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
We want to redirect both stdout and stderr to the log, so just do both redirections at once. This simplifies the call to make, which was inherited from afdb545 (tools: new tool to filter the output of make) when brmake was using unbuffer (and even then it was not entirely waranted to do the redirection that way). Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Currently, our docker-run helper will decide on its own whether it should use docker (preferred) or podman (fallback), as introduced in 9a629f5 (utils/docker-run: allow running with Podman). In case both are installed, it is not possible to exercise the podman case. Often, 'docker' is just an alias for 'podman' when both are available, but this is not always true - and in the latter case, the user needs to be able to choose which one they want. Allow the user to force the one to use, by setting the BR2_DOCKER environment variable. If that is set and it doesn't exist, exit with an explicit error message (rather than relying on the failure when eventually exec-ing the specified command). Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Ricardo Martincoski <ricardo.martincoski@datacom.com.br> Cc: Julien Olivain <ju.o@free.fr> Cc: Fiona Klute <fiona.klute@gmx.de> Reviewed-by: Fiona Klute (WIWA) <fiona.klute@gmx.de> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
This configuration builds an image for the Polyhex Debix Model A SBC DEBIX Model A is an industrial grade single board computer powered by NXP i.MX 8M Plus applications processor https://www.debix.io/hardware/model-a.html - Linux Kernel: Upstream version 6.12.14 - U-boot: Upstream version 2025.01 - ATF: Upstream version 2.12 Signed-off-by: Gilles Talis <gilles.talis@gmail.com> Signed-off-by: Julien Olivain <ju.o@free.fr>
RNNoise is a noise suppression library based on a recurrent neural network. Add an upstream post-0.2 patch to fix a build issue. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> [Julien: remove --disable-doc in _CONF_OPTS already in infra] Signed-off-by: Julien Olivain <ju.o@free.fr>
Instead of having a bool option for enabling the LZ4HC compression, change the Kconfig definition to a choice, which also adds more flexibility in the future (e.g. for enabling ZSTD compression). The name of the old option was preserved so defconfigs using it won't be affected. Also both for LZMA and LZ4HC, it's now possible to define compression level. Previously it defaulted to 9, which generates images larger than squashfs with comparable settings (which uses level 12 by default). For LZ4HC the default if unset would be still 9. Use a separate config option for LZMA and LZ4HC compression level, because their ranges and meaning are different. Signed-off-by: Jan Čermák <sairon@sairon.cz> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Add Kconfig toggles for a few more extended options that are useful for reducing size and improving performance of EROFS images. Descriptions of the config options were taken from the erofs-utils manpage. Signed-off-by: Jan Čermák <sairon@sairon.cz> [Arnout: fix Config.in help text and indentation] Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
…file Add another option for FS compression that allows fine-grained control using a list of algorithms and optional compress-hints file. This way multiple algorithms and pcluster sizes can be used for different files, fully exposing EROFS compression abilities. Signed-off-by: Jan Čermák <sairon@sairon.cz> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.1)
Can you help keep this open source service alive? 💖 Please sponsor : )