Hi Nick, I'll look into that. Thanks, Vincent On Jan 24, 2013, at 5:56 PM, "Carter, Nicholas P" <nicholas.p.carter(a)intel.com&gt; wrote: > I noticed a minor weirdness when building OCR. It looks like the default install script is passing both “-O0” and “-O2” to gcc. The “-O0” looks like it’s coming from the default OCR_CFLAGS that’s set in src/Makefile.am, but it’s not obvious to me where the “-O2” is coming from. > > Mostly, this seems like it might confuse anyone who’s trying to change the optimization level, since gcc will use the last –O value it sees. Thought I’d toss it out as a minor nit. > > Example from the output of install.sh: > > /bin/sh ../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME= > \"ocr\" -DPACKAGE_TARNAME=\"ocr\" -DPACKAGE_VERSION=\"0.7\" -DPAC > KAGE_STRING=\"ocr\ 0.7\" -DPACKAGE_BUGREPORT=\&quot;ocr-dev(a)lists.01.o > rg\" -DPACKAGE_URL=\"\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DH > AVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMOR > Y_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -D > HAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -I. -I../ > ../src -I../../inc -I../../src/inc -I../../src/inc/hc -Wall -g > -O0 -Werror -g -O2 -MT libocr_la-ocr-runtime.lo -MD -MP -MF .dep > s/libocr_la-ocr-runtime.Tpo -c -o libocr_la-ocr-runtime.lo `test > -f 'ocr-runtime.c' || echo '../../src/'`ocr-runtime.c > > -Nick > _______________________________________________ > OCR-dev mailing list > OCR-dev(a)lists.01.org > https://lists.01.org/mailman/listinfo/ocr-dev