Looking to resolve Qemu on AppleSilicon build failure
blake at netjibbing.com
Thu Feb 18 18:14:06 UTC 2021
Thanks for closing the loop on that. I'll do some testing with that PR as
it includes the needed patches to support hypervisor.framework.
On Thu, Feb 18, 2021 at 9:36 AM Rainer Müller <raimue at macports.org> wrote:
> On 18/02/2021 05.23, Joshua Root wrote:
> > On 2021-2-18 08:33 , Blake Garner wrote:
> >> I have been unsuccessfully trying to figure out how to resolve this
> issue with
> >> qemu builds on AppleSilicon hardware.
> >> https://trac.macports.org/ticket/62116 <
> >> My suspicion is that the build is not using the correct architecture
> >> setting up the include directories for part of the build. This is based
> >> some of the build log output. As noted in the ticket I was able to
> build qemu
> >> on the same system outside of MacPorts so again that points me to some
> of the
> >> configurations in the port.
> >> Any suggestions on what to look for here? Seems like I should be able to
> >> compare the output of the configure scripts to isolate differences
> between the
> >> working and not working builds?
> > Are you building with the same configure args as the port? The --cpu=
> option is
> > the first obvious thing I see that might be relevant. Maybe qemu needs
> to update
> > its config.guess and config.sub, or maybe it just wants you to say
> > instead of "arm64".
> That's it exactly, QEMU's build system expects this to be --cpu=aarch64.
> There is already an open work-in-progress pull request that addresses this,
> among other related issues for the Apple M1. It wasn't linked at the Trac
> yet, but I added that just now.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the macports-dev