From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15271] no start-qemu.sh
Date: Sat, 28 Jan 2023 20:34:54 +0000 [thread overview]
Message-ID: <bug-15271-163-8lxvFxzQnA@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15271-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15271
Thomas Petazzoni <thomas.petazzoni@bootlin.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #2 from Thomas Petazzoni <thomas.petazzoni@bootlin.com> ---
Thanks for your report, but I'm afraid there is no bug in what you're
reporting:
- We definitely need some sort of hint that tells us whether a start-qemu.sh
script should be produced or not, and we have chosen this hint to be "the
defconfig starts with qemu_". This is certainly an arbitrary choice, but we
anyway had to make an arbitrary choice. In addition, this generation of
start-qemu.sh script is really an "internal" Buildroot feature to help users
use our stock qemu_*_defconfig. For your own defconfigs, you can provide your
own start-qemu.sh script.
- The fact that .br2-external files are preserved on make clean is normal, just
like we preserve your .config file. This way, you can restart a build with the
same configuration/BR2_EXTERNAL after a "make clean". This is the intended
behavior.
--
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:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 13:54 [Buildroot] [Bug 15271] New: no start-qemu.sh bugzilla
2023-01-24 8:25 ` [Buildroot] [Bug 15271] " bugzilla
2023-01-28 20:34 ` 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-15271-163-8lxvFxzQnA@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