Il 16/09/2013 19:23, Tom Tromey ha scritto: > Tom> I can try a test build using a setting for CC that rejects -c -o. > > I did this and the build died pretty early on: > > /home/tromey/Space/Trunk/Git/bin/my-cc -c -DHAVE_CONFIG_H -g -g -I. > -I../../gcc/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat > -Wstrict-prototypes -pedantic -fpic ../../gcc/libiberty/regex.c -o > pic/regex.o; \ > else true; fi > no -c -o support > make[3]: *** [regex.o] Error 1 > make[3]: Leaving directory `/home/tromey/Space/Trunk/Git/build/libiberty' > make[2]: *** [all-stage1-libiberty] Error 2 > > > In this case the --enable-shared for libiberty was added automatically > because LTO defaults to enabled. Adding --disable-lto lets it get > further: > > /home/tromey/Space/Trunk/Git/bin/my-cc -DPACKAGE_NAME=\"\" > -DPACKAGE_TARNAME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" > -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"zlib\" > -DVERSION=\"1.1.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 > -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 > -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 > -DLT_OBJDIR=\".libs/\" -DHAVE_STDLIB_H=1 -DHAVE_UNISTD_H=1 > -DHAVE_GETPAGESIZE=1 -DHAVE_MMAP=1 -DHAVE_MEMCPY=1 -DHAVE_STRERROR=1 > -DHAVE_UNISTD_H=1 -I. -I../../gcc/zlib -g -g -c -o libz_a-adler32.o `test > -f 'adler32.c' || echo '../../gcc/zlib/'`adler32.c > no -c -o support > make[3]: *** [libz_a-adler32.o] Error 1 > make[3]: Leaving directory `/home/tromey/Space/Trunk/Git/build/zlib' > make[2]: *** [all-stage1-zlib] Error 2 > > > And indeed, zlib's configure.ac does not invoke AC_PROG_CC_C_O. > > So, maybe this has been broken a long time.
Likely. Zapping OUTPUT_OPTION sounds like the right thing to do. Paolo
