From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14826] make qemu_x86_64_defconfig stopped working
Date: Mon, 30 May 2022 23:41:54 +0000 [thread overview]
Message-ID: <bug-14826-163-qwF5xFWv0u@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14826-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14826
--- Comment #3 from buildroot@apitman.com ---
I'd say that's good news. I just tried master and it doesn't work either.
A system update just broke something on my end. I'm using Arch on kernel
5.17.9.
Is there a recommended distro to use for building buildroot?
EDIT: **A system update probably broke something on my end
--
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 prev parent reply other threads:[~2022-05-30 23:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 19:41 [Buildroot] [Bug 14826] New: make qemu_x86_64_defconfig stopped working bugzilla
2022-05-30 22:04 ` [Buildroot] [Bug 14826] " bugzilla
2022-05-30 23:40 ` bugzilla
2022-05-30 23:41 ` bugzilla [this message]
2022-05-31 9:28 ` bugzilla
2022-05-31 12:15 ` bugzilla
2022-05-31 17:48 ` bugzilla
2022-06-04 8:24 ` 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-14826-163-qwF5xFWv0u@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