From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15356] package gobject-introspection-1.72.0 fails to build
Date: Tue, 28 Mar 2023 21:13:49 +0000 [thread overview]
Message-ID: <bug-15356-163-1jlLui9jMk@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-15356-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=15356
--- Comment #2 from Jonathan Bittner <jbittner.br.bugs@gmail.com> ---
from experimenting with an image with cpu flags set to x86_64/slivermont on a
i9-9900 machine, setting "-cpu max" for qemu takes advantage of all
instructions available to the host processor and would likely fix your issue
assuming your host is at least as modern as your target architecture
--
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:[~2023-03-28 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 16:30 [Buildroot] [Bug 15356] New: package gobject-introspection-1.72.0 fails to build bugzilla
2023-03-13 16:04 ` [Buildroot] [Bug 15356] " bugzilla
2023-03-28 21:13 ` bugzilla [this message]
2023-03-31 15:51 ` bugzilla
2023-03-31 18:35 ` bugzilla
2024-06-15 15:06 ` 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-15356-163-1jlLui9jMk@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