From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15246] New: buildroot ignore my config
Date: Thu, 12 Jan 2023 09:47:34 +0000 [thread overview]
Message-ID: <bug-15246-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15246
Bug ID: 15246
Host: X86 AMD geode
Build: Ubuntu 22 X86_64
Summary: buildroot ignore my config
Product: buildroot
Version: 2022.11
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: glscene2010@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
I can successfully build when in my buildroot's config pc_x86_bios_defconfig I
set
BR2_LINUX_KERNEL_USE_DEFCONFIG=y
# BR2_LINUX_KERNEL_USE_ARCH_DEFAULT_CONFIG is not set
# BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG is not set
But when in pc_x86_bios_defconfig I do
BR2_LINUX_KERNEL_USE_CUSTOM_CONFIG=y
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="$(BR2_EXTERNAL)/board/my_company/my_board/pc_x86_bios_kernel4.19.269_defconfig"
All my settings from pc_x86_bios_defconfig will be ignored. Why?
To build I use command see console.txt
I get messages from buildroot see log2.txt
To get my config files see my_external_tree.7z
--
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-01-12 9:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 9:47 bugzilla [this message]
2023-01-12 9:49 ` [Buildroot] [Bug 15246] buildroot ignore my config 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
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@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.