From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15356] package gobject-introspection-1.72.0 fails to build
Date: Mon, 13 Mar 2023 16:04:53 +0000 [thread overview]
Message-ID: <bug-15356-163-FbMUBenFCm@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 #1 from Jonathan Bittner <jbittner.br.bugs@gmail.com> ---
gobject-introspection tries to build some of its code inside a qemu
environment. Selecting an "advanced" x86_64 architecture produces some
instructions that qemu does not understand. I'm not sure if a -cpu mode flag
could be set on qemu to enable those instructions.
--
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-13 16:04 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 ` bugzilla [this message]
2023-03-28 21:13 ` [Buildroot] [Bug 15356] " bugzilla
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-FbMUBenFCm@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.