On Sun, 21 Mar 2010 19:22:48 NightStrike wrote: > On Sun, Mar 21, 2010 at 5:20 PM, Ozkan Sezer <seze...@gmail.com> wrote: > > For some reason yet unknown to me, the gcc-provided headers > > have priority over the system provided headers and float.h is > > especially problematic: Not installing or deleting it is the solution, > > at least for now. > > If gcc headers didn't take priority, then fixincludes wouldn't work. > > The real question is why gcc forces changes to system headers instead > of working with system headers. >
Does gcc even necessarily have the system headers available to it on a clean system during a build? I don't think so...which means that gcc may not know about the system headers when it runs through the stage of installation... In other words, for it to even work with the system headers, the system headers have to be installed correctly before you do the first make install-gcc during a bootstrap... (and I know the one howto build doc says install the headers first, but unfortunately building the toolchain does not fail if you do NOT do this...) ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
