On 3/10/22 05:26, George R Goffe wrote: > gcc -DHAVE_CONFIG_H -I. -I../.. -Wno-cast-qual -Wno-conversion > -Wno-float-equal -Wno-sign-compare -Wno-undef -Wno-unused-function > -Wno-unused-parameter -Wno-float-conversion -Wimplicit-fallthrough > -Wno-pedantic -Wno-sign-conversion -Wno-type-limits > -Wno-unsuffixed-float-constants -g -O2 -Werror -MT libgnulib_a-canonicalize.o > -MD -MP -MF .deps/libgnulib_a-canonicalize.Tpo -c -o > libgnulib_a-canonicalize.o `test -f 'canonicalize.c' || echo > './'`canonicalize.c > canonicalize.c: In function 'canonicalize_filename_mode': > canonicalize.c:484:5: error: #warning "GCC might issue a bogus > -Wreturn-local-addr warning here." [-Werror=cpp] > 484 | #warning "GCC might issue a bogus -Wreturn-local-addr warning > here." > | ^~~~~~~ > canonicalize.c:485:5: error: #warning "See > <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644>." [-Werror=cpp] > 485 | #warning "See > <https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93644>." > | ^~~~~~~ > cc1: all warnings being treated as errors
You are compiling with -Werror, and therefore this warning lets the build process stop. Typically, this is a developer option. Did you use configure's --enable-compiler-warnings-are-errors option? Or have otherwise the -Werror in the CFLAGS environment? Have a nice day, Berny