I recently ran into something similar, albeit on an intel machine
running the latest macOS12 release, not an M1 machine.
In the end I 'brute force' fixed it by completely removing Xcode and the
CLT, then reinstalling both.
Chris
On 11/03/2022 3:15 pm, Steven Smith wrote:
I’m recently
I’m recently hitting a ton of configure/build failures on an M1. This is,
perhaps coincidentally, after an update to MacPorts 2.7.2. E.g. error on
sqlite3:
> configure: error: C compiler cannot create executables
Is anyone else seeing this? To the best of my knowledge I haven’t changed any
Additionally, I was thinking that the binary downloads of ports might be
codesigned. That would prevent people from all having to buy a certificate
themselves (and self-signed is not really an option, these are generally
ignored, maybe not if you mark them as trusted). You can of course also
I’ve recently moved from macOS Mojave with MacPorts to macOS Monterey with
MacPorts
I’ve had serious trouble with the application level firewall
(alf/socketfilterfw). I now suspect that one reason is that Apple is getting
stricter and stricter about only allowing binaries that have been code
