/bin/sh ../libtool --tag=CXX --mode=compile x86_64-pc-linux-gnu-g++ -DPACKAGE_NAME=\"DiffractionImage\" -DPACKAGE_TARNAME=\"diffractionimage\" -DPACKAGE_VERSION=\"6.1.1\" -DPACKAGE_STRING=\"DiffractionImage\ 6.1.1\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"diffractionimage\" -DVERSION=\"6.1.1\" -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/\" -DSTDC_HEADERS=1 -DHAVE_LIBM=1 -I. -I/usr/include/python2.7 -I/etc/java-config-2/current-system-vm/include -I/etc/java-config-2/current-system-vm/include/linux -march=native -O2 -fPIC -g -O0 -MT FrmRoutines.lo -MD -MP -MF .deps/FrmRoutines.Tpo -c -o FrmRoutines.lo FrmRoutines.cpp Please drop -g and -O0
I can try to drop the -g. All optimization drops have to be taken seriously. I had bad experience removing those -O* changes which led to scientifically wrong results.
(In reply to comment #1) > I can try to drop the -g. All optimization drops have to be taken seriously. I > had bad experience removing those -O* changes which led to scientifically wrong > results. If you want, you can add USE="custom-cflags" if the user wants custom-cflags, - O0 should be dropped by the use . So, adding also a warning is a good idea.
change commited. -g is dropped everywhere.
(In reply to comment #2) > (In reply to comment #1) > > I can try to drop the -g. All optimization drops have to be taken seriously. I > > had bad experience removing those -O* changes which led to scientifically wrong > > results. > > If you want, you can add USE="custom-cflags" if the user wants custom-cflags, - > O0 should be dropped by the use . So, adding also a warning is a good idea. It is not about warnings. People use this programs to create scientific results. Changing the optimization can lead to unforeseen results if not wrong results. Therefore I will stick to any reduction in optimization as upstream wants it.