From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15246] buildroot ignore my config
Date: Thu, 12 Jan 2023 16:09:24 +0000 [thread overview]
Message-ID: <bug-15246-163-8OGSfc5Ftk@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15246-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15246
--- Comment #2 from Arnout Vandecappelle <arnout@mind.be> ---
There are several places where it could have gone wrong.
* When you make changes to pc_x86_bios_defconfig this won't be taken into
account at all unless you run `make pc_x86_bios_defconfig` again.
* When you make changes manually in pc_x86_bios_defconfig, it's possible you
made a mistake (e.g. missed a dependency). As a result, your changes may have
been removed from the full .config. Check in the .config if those symbols are
there. In general, it's best to run `make menuconfig; make savedefconfig` and
review the changes, rather than editing the defconfig manually.
* After you make changes to the configuration, the next build will not take
into account changes, it will only build any *new* packages you added. In this
case, since you changed the linux configuration, you can run `make
linux-reconfigure` to refresh the configuration. In general you may need to do
a clean build (`make clean; make`).
--
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 prev parent reply other threads:[~2023-01-12 16:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 9:47 [Buildroot] [Bug 15246] New: buildroot ignore my config bugzilla
2023-01-12 9:49 ` [Buildroot] [Bug 15246] " bugzilla
2023-01-12 16:09 ` bugzilla [this message]
2023-01-13 4:34 ` bugzilla
2023-01-13 6:26 ` bugzilla
2023-01-16 0:54 ` bugzilla
2023-01-24 3:43 ` bugzilla
2023-01-26 5:40 ` bugzilla
2023-01-28 20:39 ` 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-15246-163-8OGSfc5Ftk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.