http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46501
LRN <lrn1986 at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lrn1986 at gmail dot com --- Comment #5 from LRN <lrn1986 at gmail dot com> 2013-04-13 15:31:21 UTC --- A gcc toolchain built on W32 for W32 (using MSys shell and make to run the buildsystem) also suffers from this. In all and any mingw builds (except for TDM's, they are patched somehow) that are built with --prefix=/mingw, the directory "/mingw/include" ends up in cpp_include_defaults list, and "/mingw/lib" - in the list that -print-search-dirs outputs for libraries. W32 interprets "/mingw" as "mingw subdirectory in the root directory of the drive on which current working directory is", so having headers in "c:/mingw/include", "d:/mingw/include", ... etc (and libraries in "c:/mingw/lib", ... etc) was, and is, strongly advised against by all gcc-for-w32 toolchain suppliers for _years_. Which likely means that this issue is old.