| Summary: | package gobject-introspection-1.72.0 fails to build | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | hydrosaure |
| Component: | Other | Assignee: | unassigned |
| Status: | RESOLVED MOVED | ||
| Severity: | normal | CC: | buildroot, yann.morin.1998 |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
hydrosaure
2023-02-25 16:30:48 UTC
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. 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 (In reply to Jonathan Bittner from comment #2) Thank you for the investigation. I think it would work in my case as well building on a R9 5950X targeting i7 broadwell. Which file would I add this "-cpu max" to ? FYI I have a series bumping gobject-introspection and libglib2 to version 1.74.0, I wonder if that might be helpful here: https://patchwork.ozlabs.org/project/buildroot/list/?series=321845&submitter=&state=*&q=&archive=both&delegate= Thank you for your report.
The issue tracker for the Buildroot project has been moved to
the Gitlab.com issue tracker:
https://gitlab.com/buildroot.org/buildroot/-/issues
We are taking this opportunity to close old issues in this old
tracker. If you believe your issue is still relevant, please
open one in the new issue tracker.
Thank you!
|