All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15271] New: no start-qemu.sh
Date: Sun, 22 Jan 2023 13:54:33 +0000	[thread overview]
Message-ID: <bug-15271-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=15271

            Bug ID: 15271
              Host: Qemu
             Build: Ubuntu 22 X86_64
           Summary: no start-qemu.sh
           Product: buildroot
           Version: 2022.11
          Hardware: All
                OS: Linux
            Status: NEW
          Keywords: FIXME
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: glscene2010@gmail.com
                CC: buildroot@uclibc.org
  Target Milestone: ---

Created attachment 9481
  --> https://bugs.busybox.net/attachment.cgi?id=9481&action=edit
usage: make BR2_EXTERNAL=/mnt/ramdisk/my_external_tree -C buildroot
my_qemu_x86_defconfig

Buildroot can't produce start-qemu.sh with my my_qemu_x86_defconfig. Why?

git clone https://github.com/buildroot/buildroot
make qemu_x86_defconfig -C buildroot
make -C buildroot

There is buildroot/output/images/start-qemu.sh (and also rootfs.ext2 bzImage).
Ok. Next:

make clean -C buildroot
#copy linux.config with new name
cp /mnt/ramdisk/buildroot/board/qemu/x86/linux.config
/mnt/ramdisk/my_external_tree/board/my_company/my_board/my_linux.config

#copy qemu_x86_defconfig with new name
cp /mnt/ramdisk/buildroot/configs/qemu_x86_defconfig
/mnt/ramdisk/my_external_tree/configs/my_qemu_x86_defconfig

nano /mnt/ramdisk/my_external_tree/configs/my_qemu_x86_defconfig
# and change BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE like this
BR2_LINUX_KERNEL_CUSTOM_CONFIG_FILE="/mnt/ramdisk/my_external_tree/board/my_company/my_board/my_linux.config",
save

make BR2_EXTERNAL=/mnt/ramdisk/my_external_tree -C buildroot
my_qemu_x86_defconfig
make -C buildroot

There is no buildroot/output/images/start-qemu.sh ("No Qemu cmd line found,
can't test"). There are buildroot/output/images/bzImage and
buildroot/output/images/rootfs.ext2 only. Why?

And also I see another thing like a bug:
--make clean doesn't remove .br2-external files--

After my success building
make clean -C buildroot
make BR2_EXTERNAL=/mnt/ramdisk/my_external_tree -C buildroot
my_qemu_x86_defconfig
make -C buildroot

I try
make clean -C buildroot

But in /mnt/ramdisk/buildroot/output/ there are 9 .br2-external... files. Why 
make clean -C buildroot
doesn't remove this files?

-- 
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

             reply	other threads:[~2023-01-22 13:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-22 13:54 bugzilla [this message]
2023-01-24  8:25 ` [Buildroot] [Bug 15271] no start-qemu.sh bugzilla
2023-01-28 20:34 ` 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-15271-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.