So, the ultimate answer proved to be totally different. After agonizing amounts of diagnosing, trying new configurations, I finally realized that there are two error messages up there:
Reason: no suitable image found. Did find:
file system relative paths not allowed in hardened programs
The first one turned out to be correct; there was, in fact, a dylib missing from my build. (One for x86_64 arch)
The second message is completely wrong, and led me down a long irrelevant path.
mackworth
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
After posting, I realized an obvious difference: I'm now building the Apple Silicon version, not the Intel one, so the "existing binary" is running under Rosetta, but the compiled one is running apple silicon.