last I noticed, AVX was in the runtime dispatch set, not the base set, so it shouldn’t matter.
the error message implies that the DLL is fundamentally broken (no entry point???).
try to reproduce this on a system WITH AVX that is otherwise identical in setup (same mingw). then you know it’s not AVX. I don’t know why you’d conclude that to begin with.
my bet is on mingw being broken or the environment being broken, oder something other than mingw being involved.
there is no evidence either way so it’s all hearsay and speculation. objection!