Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15820] make linux-menuconfig does not modify correct .config file when LINUX_KERNEL_CUSTOM_CONFIG_FILE set
Date: Tue, 24 Oct 2023 19:50:40 +0000	[thread overview]
Message-ID: <bug-15820-163-cyzLE6rCck@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15820-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=15820

Yann E. MORIN <yann.morin.1998@free.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |INVALID
             Status|NEW                         |RESOLVED
                 CC|                            |yann.morin.1998@free.fr

--- Comment #1 from Yann E. MORIN <yann.morin.1998@free.fr> ---
Garyl, All,

Thanks for your report.

> 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?

No, BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE is used as the "source" for the
configuration, it is not meant to be the "working copy", so the behaviour
you report is the expected one.

> 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 want to run:  make linux-update-defconfig   (or: linux-update-config)
See help, with:   make help

Regards,
Yann E. MORIN.

-- 
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

      reply	other threads:[~2023-10-24 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24 16:54 [Buildroot] [Bug 15820] New: make linux-menuconfig does not modify correct .config file when LINUX_KERNEL_CUSTOM_CONFIG_FILE set bugzilla
2023-10-24 19:50 ` 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-15820-163-cyzLE6rCck@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