(May 2, 2023 at 1:01 pm)HappySkeptic Wrote: -fPIC must be invoked on creation of the .o files (i.e. hwasan.o) , not just at the link stage.
Well, there doesn't seem to be a simple solution. Telling `configure` to use a known-good compiler (that comes with Debian) or to add `-fPIC` to every invocation to the compiler doesn't solve the problem, in fact, it doesn't even address it (the error stays the same).
The error seems to occur in the new part of GCC related to static analysis, which it is basically copying from LLVM. Is there a way to tell `configure` I don't want a static analyzer, that I just want the compiler? I mainly want to know whether my C++ programs compile using GCC 13.1.0, I don't need a static analyzer for that.
On Windows, I have Docker installed. I guess I will to install the GCC 13.1.0 image from the Docker hub and experiment with GCC 13.1.0 using Docker. After all, that's how I came to know about GCC 13.1.0, by the GitLab CI/CD of my AEC-to-WebAssembly compiler failing, and GitLab uses GCC through Docker. I once used to use the latest GCC through Docker. It sucks because sharing files between Docker containers and your host machine is difficult, but I guess I will have to.
I am currently trying to build GCC 13.1.0 on CygWin, I think it has already gone to the Stage 3 (so, that error with `-fPIC` doesn't occur on CygWin, but maybe some other will).
