libtool: compile: x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I. -I../include -Iinclude -I../src -g -DFFI_DEBUG -march=native -O2 -Wall -fexceptions -c ../src/debug.c - fPIC -DPIC -o src/.libs/debug.o Please drop
in general, i don't see much value in catching automatic -g if it doesn't override the user CFLAGS: - it doesn't change the generated code at all - it all gets stripped out when the package finishes installing into $D - fairly certain it adds no significant overhead to build time do you have any reason for reconsidering ?
I think the idea is that debug shouldn't _just_ turn on -g. If it does then it shouldn't be a USE flag. Looks like it also turns on -DFFI_DEBUG here so agreed.
true, USE=debug should do more than just turn on -g. if there are packages doing that, then we should file bugs to drop the USE=debug support.
(In reply to comment #1) > do you have any reason for reconsidering ? Same of Ryan's thought
