------- Comment #11 from andry at inbox dot ru 2008-08-02 20:41 ------- > /c/foo/bar is valid for *MSYS* apps. But we're talking about gcc which > is NOT a MSYS app, it is a MinGW app, i.e. native win32. /c/foo/bar is > *not* valid for such an app. Not true, for example, Mingw GCC 3.4.4 perfectly understands BOTH type of paths. You can simply test it putting paths in to environment variables like "CPATH" or in "-I" key on command line.
> In fact the whole point of MSYS is to > rewrite these paths as c:/foo/bar when invoking MinGW apps, but that is > only possible if they are passed on a command line. The gcc build > system sometimes embeds them in filenames and they won't be translated. > Thus you have to be careful to avoid using them. If all this was true, then build should be crash on early stage then first "incorrect" path come on commend line, but it wouldn't happend. I test build with "c:\" and with "c:/" paths, the build crashes the same. I think this is not a point of the bug. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36948
