On Mon, Mar 22, 2010 at 2:51 AM, NightStrike <nightstr...@gmail.com> wrote: > On Sun, Mar 21, 2010 at 7:41 PM, Doug Semler <dougsem...@gmail.com> wrote: >> 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...) >> > > Building the toolchain does in fact fail. Just, not at the all-gcc > stage (the bootstrapping stage). Do a make all-gcc. When it > finishes, do "make all". It'll die immediately asking for a valid > sysroot. >
Building with the --with-sysroot option makes the toolchain nicely relocatable, but we have this issue of gcc-provided headers having priority over the system provided headers. (and also the problem with the native toolchains that the <rootdir>/include directory not being used for the header search, too.) AFAIK, mingw.org doesn't build with sysroot option, and they don't have the problem specified in this thread, however that method of build seems to result in some relocation issues as in http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42886 The current situation of gcc on this thing is a big 'Ouch'.. ------------------------------------------------------------------------------ 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
