While attempting to track down some crashes in gstreamer plugins I found I couldn't generate debug versions of the build by enabling the "debug" use flag and installing with FEATURES="nostrip" emerge -p -v media-plugins/gst-plugins-nnnn. Reproducible: Always Steps to Reproduce: Try and examine a core file of a program that crashed in gstreamer.
Created attachment 191567 [details] Updated version of gst-plugins-base Here is the ebuild I modified to take account of USE="debug". The gst-plugins all inherit from this class.
replace-flags and append-flags only change the C(XX)FLAGS you set. You are responsible for setting the right flags. See [1]. If this bug is about the package ignoring your C(XX)FLAGS (which would not be solved by replace-flags and append-flags) then reopen this bug. And please submit changes to ebuilds as a diff (with diff -u) the next time. [1] http://www.gentoo.org/proj/en/qa/backtraces.xml
(In reply to comment #2) > replace-flags and append-flags only change the C(XX)FLAGS you set. You are > responsible for setting the right flags. See [1]. So what do you do to enable debug in a package that doesn't have an explicit debug conf option? Is the recommended solution to do a manual build and merge because that's not very useful if your trying to track crashes over an extended period. I based the changes on other builds in the tree that do things like: use debug && append-flags -O0 -g3 which means there are a number of packages in the tree needing fixing. > If this bug is about the package ignoring your C(XX)FLAGS (which would not be > solved by replace-flags and append-flags) then reopen this bug. > > And please submit changes to ebuilds as a diff (with diff -u) the next time. Sure. I only bumped the version so my overlay build would get picked over the main portage. I was unsure if emerge would go for my ebuild if it was the same version. > [1] http://www.gentoo.org/proj/en/qa/backtraces.xml
