Albert Chin wrote: > > The fix that I found is to use "xlc -E -C" instead of "xlc -E". It has the > > effect of turning the config.status lines > > > > S["NEXT_SIGNAL_H"]="\"///usr/include/sys/signal.h\"" > > S["NEXT_DIRENT_H"]="\"\"" > > > > into > > > > S["NEXT_SIGNAL_H"]="\"///usr/include/signal.h\"" > > S["NEXT_DIRENT_H"]="\"///usr/include/dirent.h\"" > > This doesn't always work. On AIX 6.1 with the IBM v10 compiler: > $ echo '#include <math.h>' > conftest.c > $ xlc -E -C conftest.c | grep math.h > #line 6 "/usr/vac/include/math.h" > #line 1 "/usr/include/math.h" > /* bos61B src/bos/usr/include/math.h 1.28.11.1 > */ > /* "@(#)30 1.28.11.1 src/bos/usr/include/math.h, libm, bos61B, b2008_06B1 > 2/4/08 03:09:39" */ > * COMPONENT_NAME: (LIBM) math header file > #line 92 "/usr/include/math.h" > * The ANSI standard requires that certain values be in math.h. > * ANSI required entries in math.h > * prototype in math.h. > #line 1324 "/usr/include/math.h" > #line 1358 "/usr/vac/include/math.h" > > This results in: > S["NEXT_MATH_H"]="\"///usr/vac/include/math.h\"" > > But this is wrong. What we want is: > S["NEXT_MATH_H"]="\"///usr/include/math.h\""
No. If the compiler's <math.h> is actually /usr/vac/include/math.h, we *do* want S["NEXT_MATH_H"]="\"///usr/vac/include/math.h\"" > else HUGE_VAL isn't found when lib/strtod.c is compiled. Can you investigate what's happening there? You are implying that /usr/include/math.h defines HUGE_VAL, whereas /usr/vac/include/math.h, which includes it, does not? And this is with "xlc -D_ALL_SOURCE"? Bruno
