At 2004-11-27T16:24:44-0800, Sorav Bansal <sbansal@stanford.edu> wrote:
> 
> > On Nov 27 23:10, Ciaran McCreesh wrote:
> > > | Assuming you use portage for installation of your programs, set add
> > > | "nostrip" to your FEATURES variable in /etc/make.conf .
> > >
> > > ...which, sadly, usually won't work since most autotools-based things
> > > call install -s rather than install.
> >
> > Since he mentioned that he was debugging "his project", I assumed he
> > would know not to do such things if he wants unstripped, debuggable
> > programs.  If that's not the case, or if he has no control over that
> > portion of the install, then no, it won't work.
> 
> 
> Thanks for your help. "My project" involves checking system rules on open
> source software (that means software distributed by gentoo).
> 
> Hence, any project that calls install -s will be troublesome for me.
> Anyways, I really appreciate your help. In case you have any suggestions
> on how to get around the install -s problem, that would be great!

Looking around /usr/share/{aclocal,auto}* it looks to me that automake
tries to honor the ${STRIP} variable set by the user as the program used
to strip binaries. Somebody else suggested replacing /usr/bin/strip with
a link to `true`. You could export STRIP=/usr/bin/true into the build
environment for the same effect.

Actually, we may want to do this in Portage when "nostrip" is set.

-- 
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
  --Ghost in the Shell