From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15246] buildroot ignore my config
Date: Sat, 28 Jan 2023 20:39:25 +0000 [thread overview]
Message-ID: <bug-15246-163-axWXJTnBDQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15246-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15246
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #7 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
There is apparently no Buildroot bug here, but instead:
- Andrei you are manually editing the defconfig file. Don't do that, unless you
are extremely familiar with Buildroot options. Please use "make menuconfig" to
change the configuration.
- As pointed out by Andreas, using $(BR2_EXTERNAL) will not work, you need to
use $(BR2_EXTERNAL_xyz_PATH) where "xyz" is the name of your external as
specified in the external.desc file.
Since there's no Buildroot bug here, I'm closing this entry.
--
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-01-28 20:39 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
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 [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-15246-163-axWXJTnBDQ@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.