From: Adam Duskett <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/gobject-introspection/Config.in: Allow RISCV_32 builds
Date: Fri, 7 May 2021 10:01:02 -0700 [thread overview]
Message-ID: <20210507170102.1896972-2-aduskett@rivian.com> (raw)
In-Reply-To: <20210507170102.1896972-1-aduskett@rivian.com>
From: Adam Duskett <aduskett@gmail.com>
Qemu 6.0.0 no longer segfaults when running qemu-riscv32. As such, it's now
possible to allow riscv32 to compile gobject-introspection.
Fixes:
http://autobuild.buildroot.org/results/668397b1df42297505e6fc8353c4752290a5628d
Signed-off-by: Adam Duskett <aduskett@rivian.com>
---
package/gobject-introspection/Config.in | 1 -
1 file changed, 1 deletion(-)
diff --git a/package/gobject-introspection/Config.in b/package/gobject-introspection/Config.in
index 57c569704e..bacf44363c 100644
--- a/package/gobject-introspection/Config.in
+++ b/package/gobject-introspection/Config.in
@@ -2,7 +2,6 @@ config BR2_PACKAGE_GOBJECT_INTROSPECTION_ARCH_SUPPORTS
bool
default y
depends on BR2_PACKAGE_HOST_QEMU_ARCH_SUPPORTS
- depends on !BR2_RISCV_32 # qemu-riscv32 segfaults in qemu-5.0.0
config BR2_PACKAGE_GOBJECT_INTROSPECTION
bool "gobject-introspection"
--
2.31.1
next prev parent reply other threads:[~2021-05-07 17:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 17:01 [Buildroot] [PATCH 1/2] package/qemu: bump version to 6.0.0 Adam Duskett
2021-05-07 17:01 ` Adam Duskett [this message]
2021-05-18 20:36 ` [Buildroot] [PATCH 2/2] package/gobject-introspection/Config.in: Allow RISCV_32 builds Arnout Vandecappelle
2021-05-08 10:13 ` [Buildroot] [PATCH 1/2] package/qemu: bump version to 6.0.0 Romain Naour
2021-05-18 20:34 ` Arnout Vandecappelle
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=20210507170102.1896972-2-aduskett@rivian.com \
--to=aduskett@gmail.com \
--cc=buildroot@busybox.net \
/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.