Martin Kinkelin
Martin Kinkelin
Oh I see. Afaik, that will be handled by LLVM in the future, but it's probably going to take some more months.
What? Using gdb on Windows wouldn't even cross my mind; I'd rather suggest compiling & debugging in a Linux VM if need be. It's just a matter of some more...
> Are you seriously suggesting that debugging with GDB in a Linux VM is more practical than simply using GDB on Windows directly? Not more practical of course, I just...
Nope, I guess it's really just a bunch of wrong `version()` paths, mainly in druntime, but finding them may be a bit tedious. I'd start by fixing any druntime/Phobos compile...
I can't even download these huge logs. - Maybe just out of memory if the compiler crashes?
Oh, this is weird, apparently some option inherited from LLVM: ``` $ ~/dlang/ldc2-e20e2064-linux-x86_64/bin/ldc2 -c ../hello.d -help-hidden | grep -- '--debug' --debug - Enable debug output --debug-ata-coalesce-frags - … $ ~/dlang/ldc-1.41.0-beta1/bin/ldc2...
God is this ugly. How about simply changing the shell once for the musl job, as already proposed earlier?
Seeing that there have been a bunch of explicit `bash` already (for Windows), an alternative might be simply using an Alpine Docker image, instead of that chroot-thing or whatever it...
We can default the Windows job shell to bash too, and explicitly select `cmd` for those Windows-specific steps.
Not needed anymore.