Build fails on Apple Silicon: attempting to link with file built for macOS-x86_64 about sonic-pi

[samaaron]

Not sure what's going on here, sorry. I just did a fresh clone and ran the mac-build-all.sh script in /app and it built just fine on my Apple Silicon machine.

[samaaron]

Perhaps you have some old build artefacts from a previous build? Did you checkout into a brand new directory or over an old directory?

[samaaron]

Also, what does the following output when you run it in a terminal for you: uname -m

[bdelacretaz]

It's a fresh empty folder, just did git clone, cd <folder>/app, ./mac-build-all.sh, so I don't think it can be old artefacts.

uname -m returns arm64

Maybe there's a difference in some tool versions?

Note that I'm not really blocked by this, I'm preparing a contribution of new synths and wanted to test them on my own build, but I can also submit a synths PR "blindly", just checking the syntax of the synthinfo.rb file.

[samaaron]

Interesting. One thing that might be different is that on my machine I specifically did not install Rosetta to ensure everything was all arm64. Perhaps there's something in the toolchain that defaults to x64 when Rosetta is present?

[emlyn]

I tried building it on my machine (M1 with Rosetta installed) from a fresh checkout. I ran into a couple of issues with it not finding my Homebrew QT5 install (it assumes Homebrew is installed in /usr/local, but mine is in /opt/homebrew), but after editing the build files I got mac-buildall.sh to run successfully to completion.

I wasn't able to run the generated app though, it gets immediately killed, and in the error report window that pops up, it says: EXC_BAD_ACCESS (SIGKILL (Code Signature Invalid)).

[samaaron]

That's useful to know, thanks. For the record I never personally use homebrew Qt - I always install it manually as you get more control over versions and updating etc.