I'm trying to debug xorg, however, portage tries not make me do so.... I did: CFLAGS="-g" CXXFLAGS="-g" FEATURES="nostrip" USE="debug" ebuild /usr/portage/x11-base/xorg-x11/xorg-x11-6.7.99.904.ebuild compile And then: CFLAGS="-g" CXXFLAGS="-g" FEATURES="nostrip" USE="debug" ebuild /usr/portage/x11-base/xorg-x11/xorg-x11-6.7.99.904.ebuild install But portage would strip the binaries anyway. I haven't tried to reproduce it with another package, but it's for sure an odd behaviour Reproducible: Always Steps to Reproduce: 1. 2. 3.
And I'm using the latest version of portage, sys-apps/portage-2.0.50-r10
Please check your build log for the following lines: Debug build turned on by USE=debug NOT stripping binaries and libraries OR the following line: Stripping binaries and libraries... USE=debug should essentially append '-g' and not strip things, without needing the C{,XX}FLAGS or FEATURES. Also please attach the full build log (bzip2'd if absolutely necessary).
Please remember to have the package name in the description, as that's the only way we currently have to indicate what it is.
I'll build a log, but I already can answer the questions. I've altered the ebuild so it won't strip anything so I can debug xorg, but a log will follow soon. It explicitly says: Stripping binaries and libraries... I also looked at: file `which Xnest`, and it would tell me that it is stripped. With appending the full build log.... what steps do you mean? compile, install and qmerge? (I'm doing this with ebuild, not with emerge)
I now compiled only with USE=debug and it honored my CFLAGS. I guess problems arise when I set things manually as well when using USE=debug. I'll try to reproduce. And as a side note, I don't think you want a log where it all goes well ;)
I cannot reproduce, even with the commandline I gave you... I'll put the bug on stay until I either can reconfirm or show that it was my fault... Sorry
reopening
xorg-server perfectly honors -g. Closing with the proper resolution
