Did you manage to fix it? Recently upgraded to Xcode 16.1 beta 3 and increased deployment target to 18.0 and facing the same issue with ___debug_main_executable_dylib_entry_point in command-line-aliases-file ;-;

Facing the same issue On Xcode 15/15.2-beta, https://github.com/capturecontext/swift-cocoa-extensions compiles in isolation, but not when it's imported as a dependency (both remote or local) to another package... I tried compiling for macOS and force disabled macro validation with defaults write com.apple.dt.Xcode IDESkipMacroFingerprintValidation -bool YES but nothing helps...

I'm experiencing both a warning and a couple of errors in my case (a custom package with a macro). The errors are "Undefined symbols" and "Linker command failed with exit code 1". These issues only occur locally, initially on Xcode15-beta6 and persist even after the Xcode15 public release. However, when I compile the same source code on CI, it builds successfully (https://github.com/capturecontext/swift-foundation-extensions/tree/swift-macros).

Same problem with Xcode 13.beta.2 on MBP 2018 i5 8GB 256GB. Some projects are working fine (one, that have been struggling from spm resolution so I couldn't build it on Xcode 12.5, works perfectly on Xcode 13+), but the one I'm paid for is not responding at all after package resolution (sometimes it crashes, sometimes just not responding), the same is valid for all my colleagues 🤡 Removing devices and simulators doesn't help.

@jbweimar, your site is down 😢