Martin Kinkelin

It might be worth trying `dub build --compiler=ldmd2` - if `ldmd2` works, it's a dub thing. Running dub with `-v` shows the compiler command-lines, which can be compared across dmd...

This is the wrong command - this creates a static library with `-lib`, no linking happening yet.

> Can you try it yourself? Sorry but no, looks too time-consuming and hardly LDC's fault. > What do you mean by "wrong command"? The error is emitted by the...

Thx for testing further - after a 2nd look, it looks like `-J -lib` is the problem. LDC accepts `-Jmy/dir` as well as `-J my/dir`, so an empty/invalid `-J` swallows...

DMD doesn't ignore an empty `-J`, it then adds an empty entry to its string import paths - I suspect with semantics being identical to `-J.` (include current working dir):...

Have you tried it without `--export-dynamic`? IIRC, they're not needed for gdb backtraces, just for the druntime one.

ldc-build-runtime is tested multiple times in CI and working just fine. Can you do a `/usr/bin/ldc2 -version`? If it doesn't support `-fvisibility=public`, it's probably quite old.

The remaining lit-test regression for `codegen/dcompute_cl_images.d` is a failing assertion in the SPIR-V translator. On my box, using latest KhronosGroup/SPIRV-LLVM-Translator@2e9f1262688462caf5035d73e6b60b0749eaef80: ``` #6 0x00007ffff7883e96 in __GI___assert_fail (assertion=0x555556db8728 "Val && \"isa used...

Thx for checking - I guess you didn't enable assertions for your LLVM build?

I've ported our LLVM CI from Azure Pipelines to GitHub Actions and verified here that it's still working: https://github.com/ldc-developers/llvm-project/pull/1