Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 186505 - Enabling debug flag should disable stripping on binaries
Summary: Enabling debug flag should disable stripping on binaries
Status: VERIFIED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
: 187227 195567 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-07-24 19:20 UTC by John J. Aylward
Modified: 2007-10-12 07:27 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John J. Aylward 2007-07-24 19:20:35 UTC 
I specifically noticed this with the ktorrent 2.2.1 package, but I'm sure it's a general portage thing.

Basically if I enable the debug flag for a specific package, it should be the same as emerging that package with the "nostrip" FEATURE enabled. I was pulling my hair out trying to figure out why I wasn't getting debug symbols when I could see the packages being compiled with debugging symbols.

It's also annoying to have to enable nostrip "globally" (even if just for that emerge session) when you only need it for a single package, not every package being emerged.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2007-07-24 19:23:33 UTC 
No way. We are not reinstating the FUBAR-ed debug.eclass behaviour.
Comment 2 John J. Aylward 2007-07-24 19:25:25 UTC 
ahh, I didn't know it was tried before. it just seems counter intuitive to have a 2 step process to enable debugging.
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2007-07-24 19:33:56 UTC 
See Bug 55708.
Comment 4 Jakub Moc (RETIRED) gentoo-dev 2007-07-31 11:51:51 UTC 
*** Bug 187227 has been marked as a duplicate of this bug. ***
Comment 5 Jakub Moc (RETIRED) gentoo-dev 2007-10-12 07:27:32 UTC 
*** Bug 195567 has been marked as a duplicate of this bug. ***