I can not replicate this on my m2 FWIW. I do have something for you try, make sure you don’t have any lingering env variables that you’re not thinking of. I have had an issue (for which I need file an issue for, thanks for the reminder) where by I have CPPFLAGS, CC, and LDFLAGS set to deal with a dependency (which has another dependency, etc.), if I have these set (and I’m quite sure it’s particular to what I’m setting) the wrong arch gets picked up in some places. iirc. (I have not tested this recently also).
That’s a total shot in the dark, but figured it’s worth calling out.
Perhaps. I tried to replicate on another machine, but could not, same ventura version, etc.
I really want to replicate this one I wonder if this is an autoconf and friends problem. Have you checked to see if your core utils are up to date?
I didn’t report this to asdf yet as I’ve had other things to do. Meanwhile I updated to macOS Sonoma, and now I can’t run Erlang 25 due to the bus error (JIT is broken), and I can’t build Erlang 26 due to this asmjit error. So I guess I should report it.
I suppose what would help kerl maintainers is to show that this problem doesn’t happen if you just do a plain ole ./configure && make after downloading the source tarball from github.
Ok, as I just commented on the issue, I’ve fixed it and it was due to my environment:
The x86 had bugged me from the start because I knew I was running in ARM mode. Turns out I had installed a second Homebrew (Intel version) according to these instructions on SO because I needed it for some QMK keyboard firmware related package. Even though my PATH was pointing to the ARM Homebrew, apparently something in the build was picking up the x86-64 version and making a mix’n’match build that understandably blew up.
After I removed the second Homebrew, my builds started passing again. Hope this is findable as a search result for anyone else who happens to do such silly things.