Skip to content

Misc utils/genrandconfig improvements

Thomas Petazzoni via buildroot buildroot 2 versions – Applied

Status from this message: Applied to master, thanks.

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest5 patches 2 repliesApplied
  2. v15 patches 1 replySuperseded

Changes in v2 from the cover letter

- Fix PATCH 3/5, which was breaking the randomness. Indeed the tuning done *after* randconfig was done by overwriting the .config entirely, instead of appending to it (open mode was "w+", while it should have been "a")

Patches in v2 Applied

#Subject and filesSizeRepliesApplied
1/5utils/genrandconfig: remove fixups related to untested CT-NG toolchainsutils/genrandconfig+0 -690 replies
2/5utils/genrandconfig: remove support for toolchain CSVutils/genrandconfig+2 -971 reply
3/5utils/genrandconfig: rework fine-tuning logicutils/genrandconfig+18 -530 replies
4/5utils/genrandconfig: do not use BR2_BACKUP_SITE for some buildsutils/genrandconfig+5 -00 replies
5/5utils/genrandconfig: improve loggingutils/genrandconfig+21 -70 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [Buildroot] [PATCH v2 0/5] Misc utils/genrandconfig improvements

Hello,

My starting point for this series was that I wanted to create some configurations that have BR2_BACKUP_SITE="", so that we do not use the Buildroot backup mirror, to ensure that upstream locations are still around.

While implementing this, I realized that all the semi-random configuration tweaks that we do in gen_config() are in fact completely overridden by "make randconfig", when genrandconfig is used without any toolchain CSV.

So I thought it was time for a bit of clean-up:

- Drop some fixups related to toolchains that are no longer tested (patch 1)

- Completely remove the support for using a toolchain CSV file. "make randconfig" support has been around for quite a while, it gives good results, so let's use that as the default now and only use fully random configurations (patch 2)

- Adapt the fine-tuning logic to the fact that "make randconfig" overwrites everything: move the fine-tuning logic *after* "make randconfig", but keep only what makes sense, since "make randconfig" already randomizes everything (patch 3)

- Implement what I wanted: set BR2_BACKUP_SITE="" for some builds (patch 4)

- Rework the logging of genrandconfig, as it is quite noisy right now, but only with irrelevant messages (patch 5)

Changes since v1:

- Fix PATCH 3/5, which was breaking the randomness. Indeed the tuning done *after* randconfig was done by overwriting the .config entirely, instead of appending to it (open mode was "w+", while it should have been "a")

Let me know what you think.

Thomas

Thomas Petazzoni (5):
utils/genrandconfig: remove fixups related to untested CT-NG
toolchains
utils/genrandconfig: remove support for toolchain CSV utils/genrandconfig: rework fine-tuning logic utils/genrandconfig: do not use BR2_BACKUP_SITE for some builds utils/genrandconfig: improve logging

 utils/genrandconfig | 268 ++++++++------------------------------------
 1 file changed, 44 insertions(+), 224 deletions(-)
Signature · 6 lines
2.46.0

_______________________________________________
buildroot mailing list
[email protected]
https://lists.buildroot.org/mailman/listinfo/buildroot