Purr Data build on Apple Silicon crashes on start (macOS Ventura 13.2.1 (22D68))

[luismrguimaraes]

I'm trying to build and run Purr Data on macOS Ventura 13.2.1 (22D68).

The build process seems to complete with success:

However, when trying to run it, the app just crashes on start.
This is what Purr Data shows before the crash on the latest commit (3e2039e):

I've also tried building in the latest release commit a2f5df4, but the problem remains:

Running the already built .dmg however, everything looks okay.

If I build with make incremental, the problem remains, but building with make light the app runs correctly.

[agraef]

Let me guess: You probably built for the M1/M2 architecture. I have been working on the M1/M2 port, but it doesn't work yet, and I don't really know why. Might be something in the externals, or the fact that we still use a prebuilt nw.js version for Intel. Therefore the builds distributed here are all for Intel cpus which run on M1/M2 Macs just fine with Rosetta 2.

[luismrguimaraes]

Yes, the chip is the M2. Forgot to include that "small" detail :D

[agraef]

Changed the title so that it reflects the actual issue. I'm keeping this open so that we can hopefully make a native Apple Silicon port work some time.

I've done further investigations, and as far as I can see, issues blocking that port are:

• There are several externals which are segfaulting in make check when compiled for Apple Silicon, and a couple more that are not covered by make check currently. The segfaults are likely related to miscompiled C calls due to the discrepancies between normal and variadic C calls on the latest ARM architectures). The core seems to be fine (a natively compiled "light" build will work, IIRC), so there's hope that we can eventually address all these issues.

• We're currently stuck with nw.js 0.67.0 due to serious regressions in later versions, and that version doesn't have an Apple Silicon build available, so we'd still rely on Rosetta for that part of the program, which is unsatisfactory. Specifically, we won't be able to have a native nw.js until either Critical nw2 regression: Major (10x) slowdown post-0.42.3 (where nw2 is enabled by default--disabling it restores original performance) nwjs/nw.js#7979 or window close event gets ignored if nw2 is disabled / process signals get ignored and NW.js crashes nwjs/nw.js#7981 gets fixed.