Bootstrap failure on ppc64
Ian Lance Taylor
iant@google.com
Tue Jun 5 13:53:00 GMT 2007
Tim Prince <n8tm@aol.com> writes:
> ERES@il.ibm.com wrote:
> > ../../gcc/libcpp/traditional.c: In function â_cpp_scan_out_logical_lineâ:
> > ../../gcc/libcpp/traditional.c:349: error: âfmacro.argsâ may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: âfmacro.nodeâ may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: âfmacro.offsetâ may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: âfmacro.argcâ may be used
> > uninitialized in this function
> > ../../gcc/libcpp/traditional.c:349: error: âfmacro.lineâ may be used
> > uninitialized in this function
> > make[3]: *** [traditional.o] Error 1
> > make[3]: Leaving directory `/home/eres/mainline_lim/build/libcpp'
> > make[2]: *** [all-stage2-libcpp] Error 2
> > make[2]: Leaving directory `/home/eres/mainline_lim/build'
> > make[1]: *** [stage2-bubble] Error 2
> > make[1]: Leaving directory `/home/eres/mainline_lim/build'
> > make: *** [bootstrap] Error 2
> So it looks like you must remove the -Werror option. Several of the
> Makefile.in files have WERROR macros which can be nulled out to avoid
> setting -Werror.
No, please initialize the fields in fmacro instead. The warning is
probably wrong but the cost of adding an explicit initialization is
low.
Ian
More information about the Gcc
mailing list