Il giorno ven, 25/03/2011 alle 22.18 -0400, Wayne ha scritto:
> one follow-up correction: it seems the better way is to set the
> RESTRICT="${RESTRICT} strip" variable like
>
> # disable stripping if debug USE flag set
> if use debug;then
> RESTRICT="${RESTRICT} strip"
> fi
>
> seeing now if it does the trick...
OK, RESTRICT seems to be read only once you are in src_compile.
trying FEATURES="${FEATURES} nostrip" ...
>
> peace, w
>
>
> Il giorno ven, 25/03/2011 alle 15.59 -0700, Mark Knecht ha scritto:
>
> > Wayne,
> > Stripping debug stuff is typical Gentoo. Search the Gentoo.org
> > docs for info on how to keep debugging symbols in the final output.
> >
> > I looked at it years ago but haven't ever actually done it
> > myself.
> >
> > HTH,
> > Mark
> >
> > On Fri, Mar 25, 2011 at 3:57 PM, Wayne <[email protected]> wrote:
> >
> > ahoy all,
> >
> > when trying to build ardour-2.9999 from the Pro-Audio
> > overlay with debugging enabled, unfortunately the debug USE
> > flag has no effect. i have confirmed this numerous times.
> >
> > there seem to be 2 problems with the ebuild:
> > 1. the debug USE flag sets a variable ARDOUR_DEBUG,
> > while the scons build system of Ardour 2.x is
> > looking for DEBUG
> > 2. even after manually fixing the above problem, at the
> > end of the build process, before installation, a
> > "strip" command runs, which i believe is removing
> > all the debugging symbols from the compiled code
> > regardless of whether the debug USE flag is set.
> > unfortunately, i do not see where this stripping is
> > set/unset in the ebuild. can anyone shed some light
> > on this?
> >
> > peace, w
> >
> >
> > --
> > http://wayne.in-giro.org
> >
> >
>
>
> --
> http://wayne.in-giro.org
--
http://wayne.in-giro.org
