Martin Kinkelin

> Looks like the problem is that it can't open the shared library file cause it is located in the apk: You mean the lib created with the linker script...

> Alright I'll look into EmuTLS. All the best! :) - Make sure to use a vanilla LLVM in that case (no custom TLS emulation) and patch this: https://github.com/ldc-developers/ldc/blob/5b0bd6865f2458b2c3fd00f7ef9652086f2d875d/driver/targetmachine.cpp#L496-L501 I...

And see https://github.com/llvm/llvm-project/blob/main/compiler-rt/lib/builtins/emutls.c for API/implementation details. It's part of LLVM's compiler-rt builtins library (`libclang_rt.builtins.a`).

The same image apparently still worked both times with GitHub Actions for the LLVM 7 job (the test isn't run for the LLVM 10 job because excluded with `BUILD_SHARED_LIBS=ON`...).

Ah, double free, definitely interesting. > on different CI machines Do you recall if it was Mac only or also happening on other OSs?

A retry attempt a few hours ago has worked, so it's apparently sporadic. Maybe just bad luck on that day, or the probability of failure has increased for some reason...

Our Android emulation requires the bfd linker (`-linker=bfd`) - for another reason -, which should also eliminate this error. Newer Android NDKs bundle lld only AFAIK (**edit**: so Termux might...

If `-linker=` doesn't work either, Termux probably doesn't ship with bfd anymore.

Ah, great find - should be fixed by Termux, I've never seen `-fuse-ld=ld` being used (but `-fuse-ld=bfd`, which somehow doesn't work for Termux IIRC).

I bet that's because CI isn't using a DMD with enabled assertions...