Maybe but figuring out my issues was probably faster, idk much about virtualizing mac os
Conversation
I bought an M1 mini last fall. Not a single problem with homebrew, Python, pyenv, or anything else. The only issue I had was I accidentally installed the wrong Go and couldn’t run the debugger. I think it must mostly be worked out by now.
1
Okay, one remaining issue: I can’t build github.com/austral/austral because of arch mismatch, but I don’t think would be surprised by that given how early in development austral is.
1
2
Thank you for trying! Is it a problem I can solve? I imagine the problem is there's no ocaml compiler for arm?
1
1
I think the error came from clang? It was arm-related. I’ll try again tomorrow and DM you. Really interested in austral. I don’t know of a relatively beginner-friendly systems language with linear types, but austral shows promise there!
1
2
Thanks! Feel free to open an issue. It might be a general Mac OS thing that has also reported, about Mac OS using a non standard symbol for stderr.
1
2
Oh let me pull up my notes real quick and I’ll add to this thread
1
2
@longtallcity I have an M1 Pro MBP. Austral itself built fine, but ran into trouble compiling its cpp output. There's a simple fix. In the compile() function in run-test.sh, I just added `sed -i '' 's/stderr/__stderrp/g' code.cpp` b/t austral and cpp build steps
1
2
OS X uses the name __stderrp as the stderr file descriptor. With that little sed command you can take the cpp output and build it happily with any C++ compiler. I've used both clang and g++ on austral output with no trouble
2
3
Why did they do this. Why.
2
2
I dealt with an arch mismatch as well. Can’t remember what fixed it. It was all a blur after a while.
But it is fixable.
For awhile I had two terminal apps, one which I made default launch in Rosetta2, mainly for brew and gcc/gfortran. But now everything is 💖✨🌟
1
2
Yeah I remember that brief time. brew was not ready.
1
2
Show replies