Looking to resolve Qemu on AppleSilicon build failure

Blake Garner blake at netjibbing.com
Thu Feb 18 20:03:10 UTC 2021


I was able to build qemu on my m1 mini with the port from the linked PR!
Should be able to test it and confirm hvf is working as expected this week.
Also I ran into an issue similar to https://trac.macports.org/ticket/60189
when trying to use the Xcode 12.5 Beta 2 command line tools to build the
qemu port. Reverting to the Xcode cli tools 12.4 worked.

Blake

On Thu, Feb 18, 2021 at 10:14 AM Blake Garner <blake at netjibbing.com> wrote:

> 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.
>
> Blake
>
> 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 <
>> https://trac.macports.org/ticket/62116>
>> >>
>> >> My suspicion is that the build is not using the correct architecture
>> when
>> >> setting up the include directories for part of the build. This is
>> based on
>> >> 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
>> "aarch64"
>> > 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
>> ticket
>> yet, but I added that just now.
>>
>> https://github.com/macports/macports-ports/pull/9955
>>
>> Rainer
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20210218/2ab16bf7/attachment.htm>


More information about the macports-dev mailing list