Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 21822 - the debug eclass is wrong in regards to debugging symbols
Summary: the debug eclass is wrong in regards to debugging symbols
Status: RESOLVED INVALID
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Unclassified (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Spider (RETIRED)
URL: http://forums.gentoo.org/viewtopic.ph...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-28 05:34 UTC by David Nielsen
Modified: 2011-10-30 22:22 UTC (History)
0 users

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 David Nielsen 2003-05-28 05:34:18 UTC
The debug eclass uses RESTRICT="nostrip" when it infact should do something in
the lines of FEATURE+=NOSTRIP.

The idea here being that we actually want to keep the debug symbols we just
spend good CPU cycles on making.

------------
# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
# $Header: /home/cvsroot/gentoo-x86/eclass/debug.eclass,v 1.18 2003/02/16
04:26:21 vapier Exp $
#
# Author: Spider
#
# A general DEBUG eclass to ease inclusion of debugging information
# and to remove "bad" flags from CFLAGS
 
# Debug ECLASS
ECLASS="debug"
INHERITED="$INHERITED $ECLASS"
# Do _NOT_ strip symbols in the build! Need both lines for Portage 1.8.9+
DEBUG="yes"
RESTRICT="nostrip"    <----------------------- ERROR ?
# Remove omit-frame-pointer as some useless folks define that all over the
place. they should be shot with a 16 gauge slingshot at least :)
# force debug information
export CFLAGS="${CFLAGS/-fomit-frame-pointer/} -g"
export CXXFLAGS="${CXXFLAGS/-fomit-frame-pointer/} -g"
# einfo "CFLAGS and CXXFLAGS redefined"
---------------

Reproducible: Always
Steps to Reproduce:
Comment 1 Spider (RETIRED) gentoo-dev 2003-06-12 09:27:36 UTC
if you wish to change the -syntax- of portage's handling of builds, you file this in the wrong place.

if you think that RESTRICT="nostrip" "doesnt work"  then I'd want a testcase, since for all I can tell the current logic works

RESTRICT=   means add the following restrictions to the build.
that means, you add exceptions to the default behaviours.


closing this as invalid. if you have a testcase where the current doesn't work, reopen with that.

if you wish to change the portage syntax for RESTRICT, file a new bug where you are a bit clearer on that point.