> Just to clarify my confusion: using the original libstdc++ > (https://github.com/geany/geany/commit/110c7b492e8595851131eeb5c381418799e8ae34) > the Lerc error still persisted?
No, it was gone, but instead I got the error in libgeany as described in https://github.com/geany/geany/pull/4094#issuecomment-2517303194 > Even if and the rest still works, I'm happy to remove this hack. Maybe the > toolchain changed since I added it a year ago. I'm afraid that depending on which libstdc++ version you use, you either get the libgeany error or the libLerc error. So what I did is that I compiled libLerc myself, statically linking the msys libstdc++ with which it works, so even when Geany is distributed with the other libstdc++, libLerc doesn't need it at the runtime. It would be possible to perform this as part of the CI build if there's no other way to get Geany running (it's just a few files to compile so not much more extra time, it just needs `cmake` and for static linking I used something like ` CXXFLAGS="-static-libstdc++" cmake ..`). Just wondering, what is this "posix" libstdc++ version? Is it something that is provided officially by the msys project? If so, we could maybe report the problem there. I also noticed that the libLerc msys binary https://packages.msys2.org/packages/mingw-w64-x86_64-lerc was built more than 2 years ago and maybe rebuilding it against the current msys libstdc++ will fix the problem. > I'm wondering why I don't see these errors, I think the only difference is > that I'm on oldish Windows 7. No idea :-/ -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/4094#issuecomment-2525223875 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/4094/[email protected]>
