From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15856] Using BR2_CONFIG= on a different file-system than O= (build outputs) fails with kconfig syncconfig error
Date: Sat, 18 Nov 2023 16:17:17 +0000 [thread overview]
Message-ID: <bug-15856-163-Uzdlbl15fE@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15856-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15856
Arnout Vandecappelle <arnout@mind.be> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #1 from Arnout Vandecappelle <arnout@mind.be> ---
> and one also specifies `BR2_CONFIG`
BR2_CONFIG is not something that is supposed to be overridden. It is supposed
to reside in the same location as the output directory.
We will not accept patches that fix this specific problem you have.
What is your use case for putting the configuration file outside of the output
directory? Perhaps we can find a better solution for this specific use case.
However, please discuss this on the mailing list [1] rather than in the bug
tracker.
[1] https://lists.buildroot.org/mailman/listinfo/buildroot
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-18 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 8:59 [Buildroot] [Bug 15856] New: Using BR2_CONFIG= on a different file-system than O= (build outputs) fails with kconfig syncconfig error bugzilla
2023-11-18 16:17 ` bugzilla [this message]
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=bug-15856-163-Uzdlbl15fE@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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