From: Sorav Bansal <sbansal@stanford.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: Re: Disabling "strip" in Emerge
Date: Sat, 27 Nov 2004 16:24:44 -0800 (PST) [thread overview]
Message-ID: <Pine.GSO.4.44.0411271559440.1025-100000@elaine27.Stanford.EDU> (raw)
In-Reply-To: <20041127232254.GA358@halffull.org>
> 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!
Sorav
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-11-28 0:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-27 22:23 [gentoo-portage-dev] Disabling "strip" in Emerge Sorav Bansal
2004-11-27 22:43 ` [gentoo-portage-dev] " Thomas Kirchner
2004-11-27 23:10 ` Ciaran McCreesh
2004-11-27 23:22 ` [gentoo-portage-dev] " Thomas Kirchner
2004-11-28 0:24 ` Sorav Bansal [this message]
2004-11-28 0:28 ` Ciaran McCreesh
2004-11-28 11:48 ` Christian Parpart
2004-11-28 15:57 ` Aaron Walker
2004-11-28 19:33 ` Paul de Vrieze
2004-11-28 23:29 ` Drake Wyrm
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.GSO.4.44.0411271559440.1025-100000@elaine27.Stanford.EDU \
--to=sbansal@stanford.edu \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox