ld Assertion failed: (target->definition() != ld::Atom::definitionProxy) while building Haskell project

You’ve clearly tripped an assertion within the linker. That is, by definition, a bug in the linker [1], and I’d appreciate you filing it as such. You’ll get more traction if you attach the build artefacts required to reproduce the problem (that is, all the .o files) because I don’t think our linker engineers have Haskell installed (-: Oh, and the assertion references a file, /tmp/libHSfuturice-integrations-0-inplace-ghc8.10.7.dylib-2022-00-08-222023.ld-snapshot, that’s likely to be helpful.

Please post your bug number, just for the record.

The backtrace you posted suggests that this is related to chained fixups, a new feature that’s on by default on modern systems. I know that you’re running the linker an Apple silicon, but are you also building for Apple silicon? Or are you building for Intel on Apple silicon?

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

[1] Even if GHC is doing something wrong, the linker should print a nice diagnostic rather than crash.

Thanks! Filed feedback with the output and /tmp/...ld-snapshot contents. Bug number is 9839914.

Yes, building for Apple silicon on Apple silicon.

$ ghc --info
 ,("target platform string","aarch64-apple-darwin")
 ,("target os","OSDarwin")
 ,("target arch","ArchAArch64")
 ,("LLVM target","arm64-apple-darwin")
 ,("Build platform","aarch64-apple-darwin")
 ,("Host platform","aarch64-apple-darwin")
 ,("Target platform","aarch64-apple-darwin")

Bug number is FB9839914.

Thanks.

Yes, building for Apple silicon on Apple silicon.

OK.

Given that, I have one suggestion that might lead to a short-term workaround. If you set your deployment target to macOS 11 (currently I suspect it’s defaulting to macOS 12), does that help? You can do this using the -macos_version_min option, documented in the ld man page.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

I tried -optl-mmacosx-version-min=11.0 and MACOSX_DEPLOYMENT_TARGET=11.0 which both resulted in many warnings like ld: warning: dylib (/opt/homebrew/lib/libpq.dylib) was built for newer macOS version (12.0) than being linked (11.0) followed by the same ld assertion failure.

Yeah, that’s a challenge. Homebrew builds from source and always sets the deployment target to the current system version, and the linker gets grumpy if you try to mix deployment targets (and rightly so!).

You could try building your dependencies on macOS 11, then copying them across to macOS 12, then re-running this test. Honestly though, I’m not sure it’s worth the effort going further down this path because…

I got some preliminary feedback on your bug report. Earlier I wrote:

Even if GHC is doing something wrong, the linker should print a nice diagnostic rather than crash.

It seems that GHC is doing something wrong and our resolution for this bug will be to convert that assert into a proper error message. You should get the details via official channels soon. If you don’t hear from our bugs folks by this time next week, drop me a line via email (my email address is in my signature; also, make sure to reference this thread ’cause I get way too much email :-).

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"