[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-11 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #11 from Costas Argyris --- As I said before, I think adding the "-o" flag to $(COMPILER) -c $< -o $@ is a good and harmless change, but, as per your own report, it didn't solve your issues because you still got that mysterious lin

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-11 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #10 from Costas Argyris --- Hi Huaqi, This is building a larger project, which gcc is part of.I am not familiar with that larger project and I have never built it. Could we extract only the gcc-specific part out of the entire b

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-11 Thread fanghuaqi at vip dot qq.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #9 from Huaqi --- Hi, Costas Argyris, I am using this repo to help build toolchain, the repo link is here: https://github.com/riscv-collab/riscv-gnu-toolchain clone this source code and its submodule, and change gcc to upstream ve

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-11 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #8 from Costas Argyris --- Are you building the cross-compiler itself or just using an existing cross-compiler to build for the windows host? You may have to build the cross-compiler first from the latest gcc sources, and then use t

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-11 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #7 from Costas Argyris --- Still can't do much without detailed info on how exactly you are building gcc, what is your build setup, what is your cross-compiler version, OS, how you configure etc etc...Ideally, solid reproduction

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-10 Thread fanghuaqi at vip dot qq.com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #6 from Huaqi --- I think it might be introduced by this commit https://github.com/gcc-mirror/gcc/commit/304c7d44a2212e6fd618587331cea2c266dc10bf, since I tested this commit https://github.com/gcc-mirror/gcc/commit/4872e46e080c6695df

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-10 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #5 from Costas Argyris --- >> Yes, because -o is missing. I don't understand why -o missing is a problem some times but not others (because this has been succesfully built before with -o missing). Adding a "-o" flag seems OK to me

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-10 Thread ebotcazou at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 Eric Botcazou changed: What|Removed |Added Status|NEW |WAITING --- Comment #4 from Eric Botcaz

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-10 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #3 from Costas Argyris --- "The missing -o looks genuine, does not it?" Not to me because this has been built successfully before.If this was the problem then it would never build, right? What happened in this case was that sym

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-10 Thread ebotcazou at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 Eric Botcazou changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c/109460] Build gcc for win32 failed in gcc13 master branch

2023-04-10 Thread costas.argyris at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460 --- Comment #1 from Costas Argyris --- Can you give some more info on how exactly you are cross-building gcc for windows host? Did you add the -fno-PIE flag manually or was it part of the build process you are following? Seems like you are try