> Hmm. If that's true, MacPorts doesn't support that yet. Let's see if it solves this fellow's problem. Many similar reports on Google about this error in this situation, with this solution.
Turning off stack checking is a blunt fix, to be sure. That symbol is found by dyld at runtime ... didn't grep it in my libSystem.dylib on Catalina, though. Still looking for it. Indeed -- odd that this wouldn't be handled by Xcode and/or ld64 automatically based on deployment target... maybe it is. Some reports said it was meant to be a weak-linked symbol, which would make sense. If so, some software builds might override that with no-weak or similar issues, and cause errors. Ken
