p0nce

locale dependency in `strtod` in Wren caused problems for us in `wren-port`. I would recommend replacing double parsing in Wren by something indenpendent from C stdlib locale.

Going further, if we force ld to output arm64: ``` % ldc2 main.d -march arm64 -L=-arch -L=arm64 ld: warning: ignoring file /Users/ponce/Desktop/compilers/ldc2-1.22.0-osx-x86_64/lib/libphobos2-ldc.a, building for macOS-arm64 but attempting to link with...

Consider the following `main.d`: ``` void main(string[]args) { import std.stdio; writeln("hello Big Sur"); } ``` In `ldc2.conf`, cheat in the following way. We just reuse stdlib built for iOS. ```...

Noted. I'll let you know how the runtime building goes. The good news is that on the DUB side there isn't too much to do, just doing `dub test -a...

A bit chicken and egg: to build runtime for arm64-apple-macos you need a private SDK `/Applications/Xcode-beta.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX11.0.sdk`, not sure when it will be distributed publicly.

Yes, with strong probability the macOS 11.0 SDK is available in this beta.

Re. building the runtime: I got the furthest with the following cmdline: `./ldc-build-runtime -j8 --dflags="-mtriple=arm64-apple-macos" --cflags="--target=arm64-apple-macos" --linkerFlags="-arch;arm64"` (Note: I'm using LDC 1.22) (Other flag combinations have conflicts between arch decided...

Yes, and there are a few other places like this in druntime, special-casing older OSX. Going to sleep, thanks for your help! (and it's not always clear when the new...

In any case I'll need to cross-check between `x86_64` and `arm64`, maybe the symbols could be different. (EDIT: yes, they are)

It's everything related to shared libraries that makes me anxious @jacob-carlborg. What problems can you foresee?