https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109460
--- Comment #3 from Costas Argyris <costas.argyris at gmail dot com> --- "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-mingw32.o was treated as an input to the compiler (see "No such file or directory" error) rather than as an output which it really is. I suspect this had to do with -fno-PIE triggering building an executable, which I still don't know where it is coming from and whether it should be used for compiling this file, as this has nothing to do with an executable - we are only compiling the .cc file to a .o file. Still I think it is important to have details of the overall build process followed to get some context.
