Re: [proaudio] ardour-2.9999 debug build problems ...

[Dominique Michel <dominique.michel@xxxxxxxxx>]

Le Mon, 28 Mar 2011 21:13:35 -0400,
Wayne <wayne@xxxxxxxxxxx> a écrit :

> thanks Dominique.  from that document, it seems like the debug USE
> flag is actually not meant to create a debug build of the package,
> only as a "a last-chance card".  so now i am totally confused ;)
> there seems to be no automated way that my weak ebuild skills can
> conjure up to make the ardour-2.9999 ebuild prevent stripping if the
> debug USE flag is enabled.  my last attempt, setting
> FEATURES="nostrip" in response to the debug flag being set, have done
> nothing.
> 
>     anyone have more suggestions?  or does one really have to use
> FEATURES="${FEATURES} splitdebug" manually every time a debug build is
> required?  it seems odd that a debug use flag produces a binary
> without debug symbols?

debug flags are USE flags. They change the way specific softwares are
configured before compiling. As such, you must enable the debug use flag
only if it is required by upstream to make a valid bug report.

In general but not always, the debug USE flag change nothing to a
backtrace content, it is only adding more verbose comments at the
console when the program is running.

FEATURES are general compilation options. You can enable them globally
in make.conf, but if you don't want it, it is no other way than to use

FEATURES="${FEATURES} splitdebug" emerge xyz

In fact, this is not a problem because you also need CFLAGS="-ggdb".

You can put the command into a script somewhere in $PATH:

#!/bin/sh
FEATURES="splitdebug" CFLAGS="-ggdb" emerge -a mplayer

From "man make.conf", it should maybe be possible to
use /etc/portage/package.env (The description of this in "man portage"
is very succinct...) instead. But I never experimented with it.

 Dominique

> 
>     thanks again.
> 
> peace, w
> 
> 
>     
> Il giorno sab, 26/03/2011 alle 13.59 +0100, Dominique Michel ha
> scritto: 
> 
> > Le Sat, 26 Mar 2011 05:09:48 -0700,
> > Mark Knecht <markknecht@xxxxxxxxx> a écrit :
> > 
> > This is also this doc:
> > http://www.gentoo.org/proj/en/qa/backtraces.xml
> > 
> > From it, you must have USE="". You can have
> > FEATURES=splitdebug instead of nostrip, but cannot have both.
> > 
> > You have also some explanation about the debug USE flag.
> > 
> > Ciao,
> > Dominique
> > 
> > 
> > > On Fri, Mar 25, 2011 at 7:38 PM, Wayne <wayne@xxxxxxxxxxx> wrote:
> > > >
> > > > Il giorno ven, 25/03/2011 alle 19.29 -0700, Mark Knecht ha
> > > > scritto:
> > > >
> > > > FEATURES="nostrip" emerge XXX
> > > >
> > > > with whatever use flags you want set in package.use will likely
> > > > get you close. TTBOMK you don't have to modify ebuilds to do
> > > > this. You just have to jump through some number of hoops.
> > > >
> > > >     true.  however, we want the debug USE flag to actually make
> > > > all this happen automatically, rather than forcing the user to
> > > > remember to adjust the FEATURES variable each emerge.  there
> > > > are obviously scenarios where both would make sense.  however,
> > > > when i enabled the debug USE flag, i expected a debug build of
> > > > the package.  are there other interpretations of the debug USE
> > > > flag that i am missing?
> > > >
> > > >     thanks for all your feedback.
> > > >
> > > > peace, w
> > > >
> > > 
> > > Being that I'm not a developer I've never tried to understand the
> > > reasoning. As a 12 year Gentoo user I can just say that for
> > > whatever reason it's always been that way since I started with the
> > > distribution.
> > > 
> > > Cheers,
> > > Mark
> > > 
> > > 
> > 
> > 
> 
> 


-- 
"We have the heroes we deserve."