> I agree, and I read the threads about that there on mingw.org. I > don't see a good chance that it get fixed soon there. Nevertheless is > the msys-environment the only way to do a full bootstrap of native gcc > toolchain, so I would simply love to have this work-a-rounded it in > gcc. But well, I won't die if it isn't. ;)
You can use other environments (e.g. cygwin or interix) to build native gcc under Windows, with a bit of tweaking. > Yes, understood. But some lines down in Makefile we use LN_S with same > pathes, but with filenames on all two arguments. So I think this fear > might be without reason here. (see section "Copy new target dependent > sources"). The section you are referring to concerns a different and much smaller set of files, so will not be affected by command line limitations, so this is not comparable. Arno
