This is the mail archive of the
automake@gnu.org
mailing list for the automake project.
Re: automake 1.4g: About `make install-strip'
- To: Alexandre Oliva <oliva at lsd dot ic dot unicamp dot br>
- Subject: Re: automake 1.4g: About `make install-strip'
- From: "Maciej W. Rozycki" <macro at ds2 dot pg dot gda dot pl>
- Date: Mon, 28 May 2001 22:58:44 +0200 (MET DST)
- cc: Tom Tromey <tromey at redhat dot com>, automake at gnu dot org
- List-Id: Discussion list for automake <automake.gnu.org>
- Organization: Technical University of Gdansk
On 28 May 2001, Alexandre Oliva wrote:
> > Well, that actually handles one half of the problem (yes, I do cross
> > builds regularly)..
>
> So do I. But then, I don't use install-strip on them.
I do as I cross-build RPM packages. And it works.
> In any case, I don't know of any way to convince the system install
> program to run a particular strip program, as opposed to plain
> `strip'. So this is as good as it gets, unless we go for MAYBE_STRIP,
> which comes with its own problems, as you have pointed out.
I was thinking of a configure-time check if `install -s' works. Then if
install has an appropriate strip program available, it would succeed.
Otherwise we could fall back to install-sh. For example I have
$tooldir/bin first in the PATH environment variable when doing
cross-builds, so `install -s' succeeds for me.
Since Tom was not very happy with the idea, I thought another possibility
is to extend install so it can be instructed to use a specific program to
strip. The install program is a part of fileutils -- there should be no
technical problem with making any changes.
--
+ Maciej W. Rozycki, Technical University of Gdansk, Poland +
+--------------------------------------------------------------+
+ e-mail: macro@ds2.pg.gda.pl, PGP key available +