From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15820] New: make linux-menuconfig does not modify correct .config file when LINUX_KERNEL_CUSTOM_CONFIG_FILE set
Date: Tue, 24 Oct 2023 16:54:21 +0000 [thread overview]
Message-ID: <bug-15820-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15820
Bug ID: 15820
Summary: make linux-menuconfig does not modify correct .config
file when LINUX_KERNEL_CUSTOM_CONFIG_FILE set
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: gary.isliefson@ametek.com
CC: buildroot@uclibc.org
Target Milestone: ---
I want to have the linux source files in an alternate tree from where buildroot
places them after the download. I've successfully done this by using the
local.mk file with an entry LINUX_OVERRIDE_SRCDIR=/home/me/some-path.
make linux-rebuild then correctly builds from the source files in the new path.
However, if I run make linux-menuconfig, it modifies the .config file in its
build directory (which is under buildroot at output/build/linux-custom/.config)
I found the variable BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE in buildroot's make
menuconfig, and I thought this would do what I want (ie, modify the .config in
my linux source directory), so I set this var to
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE=/home/me/some-path/.config
Then make linux-reconfigure, it rebuilds linux, but appeared to again use the
wrong .config file, then make linux-menuconfig still modifies the .config in
output/build/linux-custom, rather than modifying the one in my source directory
(/home/me/some-path/.config).
Correct me if I'm wrong, but setting BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE
shouldn't buildroot make linux-menuconfig modify the one pointed to by this
variable? So far, I've had to run make linux-menuconfig, then manually copy the
output/target/linux-custom/.config to my actual linux source directory in order
to preserve the changes.
--
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
next reply other threads:[~2023-10-24 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 16:54 bugzilla [this message]
2023-10-24 19:50 ` [Buildroot] [Bug 15820] make linux-menuconfig does not modify correct .config file when LINUX_KERNEL_CUSTOM_CONFIG_FILE set bugzilla
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-15820-163@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