From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 15356] New: package gobject-introspection-1.72.0 fails to build
Date: Sat, 25 Feb 2023 16:30:48 +0000 [thread overview]
Message-ID: <bug-15356-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=15356
Bug ID: 15356
Summary: package gobject-introspection-1.72.0 fails to build
Product: buildroot
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned@buildroot.uclibc.org
Reporter: hydrosaure@gmail.com
CC: buildroot@uclibc.org
Target Milestone: ---
Hello,
When building with target architecture "x86_64" and setting an architecture
variant as anything other than "x86_64" ie. "haswell" or "broadwell", package
"gobject-introspection" fails to build and ends erroring out with messages
like:
qemu: uncaught target signal 4 (Illegal instruction) - core dumped
Illegal instruction (core dumped)
Many examples of this error can be found on the buildbot at
http://autobuild.buildroot.org/?arch=x86_64&reason=gobject-introspection-1.72.0&step=50&start=0
and checking out endlog data.
When building with target architecture "x86_64" and architecture variant
"x86_64" it completes correctly.
Could it be there is some confusion between host and target for the wrapper
commands?
--
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 reply other threads:[~2023-02-25 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 16:30 bugzilla [this message]
2023-03-13 16:04 ` [Buildroot] [Bug 15356] package gobject-introspection-1.72.0 fails to build bugzilla
2023-03-28 21:13 ` 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@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