From: Earnie B. <ea...@us...> - 2012-02-13 19:45:35
|
On Mon, Feb 13, 2012 at 12:28 PM, Eli Zaretskii <el...@gn...> wrote: >> Date: Mon, 13 Feb 2012 07:46:24 -0500 >> From: Earnie Boyd <ea...@us...> >> >> > I'm compiling a C program that sets floating point control word: >> > >> > <test.c> >> > #include <float.h> >> > >> >> This is c:/mingw/lib/gcc/[GCC-VERSION]/mingw32/include/float.h which >> isn't kind enough to ``#include_next <float.h>'' > > Shouldn't it be the other way around? That is, shouldn't MinGW header > #include_next the one from GCC? > It does already. The issue is that GCC has a regression that chooses its library header first. > At least on my machine (which uses such an ancient version of GCC that > I'm embarrassed to say which one) this is so. Yes, it used to work just fine. IIRC, Keith told me that GCC used to do what I suggested above. I can't find the reference to what I'm think of though. -- Earnie -- https://sites.google.com/site/earnieboyd |