From: David Laight <david.laight@aculab.com>
To: buildroot@busybox.net
Subject: [Buildroot] BR2_PACKAGE_BUSYBOX_CONFIG ignored
Date: Fri, 14 May 2021 04:11:02 -0500 (CDT) [thread overview]
Message-ID: <1620983462705-0.post@n4.nabble.com> (raw)
AFAICT the filename passed in BR2_PACKAGE_BUSYBOX_CONFIG is ignored and the
.config file in output/build/busybox-1.33.0 is always read and then
rewritten.
There is a lot of makefile 'goop' to read through, so I'm not sure how it is
expected to get passed through.
A quick look at the busybox config sources seemed to imply that NULL was
passed in as the old config file name - so it always looked for a default
(.config or /dev/null).
--
Sent from: http://buildroot-busybox.2317881.n4.nabble.com/
next reply other threads:[~2021-05-14 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 9:11 David Laight [this message]
2021-05-14 14:59 ` [Buildroot] BR2_PACKAGE_BUSYBOX_CONFIG ignored Peter Korsgaard
2021-05-14 15:29 ` David Laight
2021-05-14 16:18 ` Peter Korsgaard
2021-05-17 9:30 ` David Laight
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1620983462705-0.post@n4.nabble.com \
--to=david.laight@aculab.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox