> @eht16 what version of g++/libstdc++ is used for windows, nowhere does the > version get printed in configure or build, grrrr?
In https://github.com/geany/geany/actions/runs/6322193707/job/17167381804?pr=3551#step:9:23 we show basic build environment information. Adding the gcc/g++ version is easy, maybe also the libstdc++ version as well. Anything else you are missing? >From the log of the image build, gcc 10.2 and libstdc++6 10.2 is used. Is gcc 10 fine in general? We could upgrade the Mingw64 build image to Debian Bookworm (currently Bullseye) to get newer gcc versions but on my last attempt this caused weired errors and so I decided to postpone it to after the release. > The CI build is now running It's running only because I added a workaround in https://github.com/geany/infrastructure/pull/10 to the image build which worked and I accidentally pushed the resulting image to the registry, so it can now be used for other builds. This is OK for the moment but I would still like to know the background of the /etc/mtab problem. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/pull/3551#issuecomment-1738444498 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/pull/3551/[email protected]>
