From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15241] post-build.sh PC grub config
Date: Sat, 28 Jan 2023 20:44:13 +0000 [thread overview]
Message-ID: <bug-15241-163-7AdQbkmJyw@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15241-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15241
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Which post-build.sh script are you talking about?
post-build.sh scripts provided in Buildroot upstream are bound to a specific
defconfig. They are not meant to be generic and valid for all situations.
If we assume that you're talking about ./board/pc/post-build.sh, then this
script is used by configs/pc_x86_64_bios_defconfig (which enables
BR2_TARGET_GRUB2_I386_PC=y) and by configs/pc_x86_64_efi_defconfig (which
enables BR2_TARGET_GRUB2_X86_64_EFI=y).
Therefore, this post-build.sh script is never used in a situation where both
BR2_TARGET_GRUB2_I386_PC and BR2_TARGET_GRUB2_I386_EFI are used. Consequently,
there is no bug.
If you create your own defconfig, which enables both BR2_TARGET_GRUB2_I386_EFI
and BR2_TARGET_GRUB2_I386_PC, you need to provide your own post-build.sh
script.
--
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:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 9:26 [Buildroot] [Bug 15241] New: post-build.sh PC grub config bugzilla
2023-01-28 20:44 ` 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-15241-163-7AdQbkmJyw@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.