From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A0899C38142 for ; Sat, 28 Jan 2023 20:35:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 2B89F81E63; Sat, 28 Jan 2023 20:35:00 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 2B89F81E63 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXK8ByScuI7F; Sat, 28 Jan 2023 20:34:59 +0000 (UTC) Received: from ash.osuosl.org (ash.osuosl.org [140.211.166.34]) by smtp1.osuosl.org (Postfix) with ESMTP id 2C32581E50; Sat, 28 Jan 2023 20:34:58 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp1.osuosl.org 2C32581E50 Received: from smtp4.osuosl.org (smtp4.osuosl.org [140.211.166.137]) by ash.osuosl.org (Postfix) with ESMTP id 3322B1BF327 for ; Sat, 28 Jan 2023 20:34:56 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp4.osuosl.org (Postfix) with ESMTP id 059AB41743 for ; Sat, 28 Jan 2023 20:34:56 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org 059AB41743 X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp4.osuosl.org ([127.0.0.1]) by localhost (smtp4.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6pPfpbNePowF for ; Sat, 28 Jan 2023 20:34:55 +0000 (UTC) Received: from busybox.osuosl.org (busybox.osuosl.org [140.211.167.122]) by smtp4.osuosl.org (Postfix) with ESMTP id D5E3D41735 for ; Sat, 28 Jan 2023 20:34:54 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 smtp4.osuosl.org D5E3D41735 Received: by busybox.osuosl.org (Postfix, from userid 81) id B4B0E87C90; Sat, 28 Jan 2023 20:34:54 +0000 (UTC) From: bugzilla@busybox.net To: buildroot@uclibc.org Date: Sat, 28 Jan 2023 20:34:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: buildroot X-Bugzilla-Component: Other X-Bugzilla-Version: 2022.11 X-Bugzilla-Keywords: FIXME X-Bugzilla-Severity: normal X-Bugzilla-Who: thomas.petazzoni@bootlin.com X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: WONTFIX X-Bugzilla-Priority: P5 X-Bugzilla-Assigned-To: unassigned@buildroot.uclibc.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.busybox.net/ Auto-Submitted: auto-generated MIME-Version: 1.0 Subject: [Buildroot] [Bug 15271] no start-qemu.sh X-BeenThere: buildroot@buildroot.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Discussion and development of buildroot List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: buildroot-bounces@buildroot.org Sender: "buildroot" https://bugs.busybox.net/show_bug.cgi?id=15271 Thomas Petazzoni changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WONTFIX Status|NEW |RESOLVED --- Comment #2 from Thomas Petazzoni --- 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