It would prove handy for the ebuild system to automatically "inherit debug" upon the declaration of "debug in the USE flags. Since I USE="debug", this would be very handy, for I try to report as many complete complete stack traces from crashes as I can. Furthermore, since many applications grab their C(XX)FLAGS from the environment as established by configure, there is no rational reason for not having "inherit debug" occur at some top level above the ebuild, for it would simply be too much of a hassle to append "debug" to all of the ebuilds IUSE declaration. Reproducible: Always Steps to Reproduce: 1.Set FEATURES="nostrip" USE="debug" in /etc/make.conf 2.Include "-fomit-frame-pointer" in CFLAGS in /etc/make.conf 3.emerge an application which does not have explicit IUSE="debug" support--e.g., lynx. Actual Results: Notice how the "-fomit-frame-pointer" remains in the CFLAGS during the Lynx build; this should not occur. The debug eclass explictly removes "-fomit-frame-pointer" Expected Results: Bad CFLAGS--e.g., "-fomit-frame-pointer"--to be stripped and debugging flags "-g" appended to CFLAGS for all ebuilds. This would really make the lives of testers very easy.
Could somebody please fix this? It would make the lives of those of us in the GNOME bugsquad much easier, as we wouldn't have to write a short essay to each crash bug reporter on gentoo user on how to rebuild all of GNOME with debugging symbols turned on and symbols not stripped from the binaries.
i personally dont think this should happen the meaning of USE=debug varies from package to package ... often times it's whatever debug code the developer has designed themselves
*** This bug has been marked as a duplicate of 55708 ***
