From what I see from my currently running xmule emerge, it adds the -g compile flag (for debug symbols generation)... and probably it shouldn't. My CFLAGS in make.conf is: -Os -pipe ex: g++ -DHAVE_CONFIG_H -D__GSOCKET_STANDALONE__ -I. -I. -I.. -D__GTK2__ -march=pentium2 -Os -pipe -g -I/usr/lib/wx/include/gtk2-2.4 -DGTK_NO_CHECK_CASTS -D__WXGTK__ -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Isrc -c -o Preferences.o `test -f 'Preferences.cpp' || echo './'`Preferences.cpp Reproducible: Always Steps to Reproduce: 1. emerge xmule 2. 3. Expected Results: no -g on compile commande line
Hello, I don't mess with changing the default xmule compilation flags for various reasons: Some flags (e.g. -O3) are known to completly break xmule and I don't feel like filtering out x flags in the ebuild Additionally, flags like -g are useful for software packages that are known to be more-or-less buggy (and believe it or not, xmule is one of those, some problems were inherited from emule also) but xmule is not an application where you would have an benefit of optimizing etc. since the only thing that matters in xmule is your network connection ;) So, if you don't come up with a reason why it should be removed I will keep this as WONTFIX. I hope my explanation satisfies you.
