Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 79481 - Portage should not run strip for packages that have the debug flag set.
Summary: Portage should not run strip for packages that have the debug flag set.
Status: RESOLVED DUPLICATE of bug 55708
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Portage team
URL: http://forums.gentoo.org/viewtopic.ph...
Whiteboard:
Keywords:
: 145127 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-01-25 08:47 UTC by Alexandre Oliveira
Modified: 2006-08-26 02:08 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandre Oliveira 2005-01-25 08:47:47 UTC
If I set debug flag in some packages (using packages.use), it means I want these packages to have the debug symbols. However, portage runs strip on them after compiling, making the debug useflag useless.
I'm aware I can put FEATURES="nostrip" in make.conf, but I do want it to run in all my packages, except the few ones I need to debug. 

In my opinion, strip should not run if the debug flag is set.

Reproducible: Always
Steps to Reproduce:
1.Set the use flag debug for some package in packages.use;
2.emerge this package. Portage will run strip at the end (unless the ebuild tells it not to);
Actual Results:  
The program doesn't have debug symbols.

Expected Results:  
As the debug flag is set, the symbols should be there.
Comment 1 solar (RETIRED) gentoo-dev 2005-02-28 08:56:28 UTC
I'm not sure if it's a good idea to set a new presidence by allowing USE flags to control FEATURES=
Comment 2 Jason Stubbs (RETIRED) gentoo-dev 2005-05-16 06:34:03 UTC

*** This bug has been marked as a duplicate of 55708 ***
Comment 3 Jakub Moc (RETIRED) gentoo-dev 2006-08-26 02:08:35 UTC
*** Bug 145127 has been marked as a duplicate of this bug. ***