Hello,
On Thu, Aug 18, 2005 at 05:50:15PM +0200, Harald Dunkel wrote:
> Would it be possible to strip libraries at install
> time? Or do I have to set CFLAGS/CXXFLAGS?
if I understand correctly, "make install-strip" strips libtool libraries
(LTLIBRARIES). (see /usr/share
Hi folks,
Would it be possible to strip libraries at install
time? Or do I have to set CFLAGS/CXXFLAGS?
Regards
Harri
On 28 May 2001, Alexandre Oliva wrote:
> > I was thinking of a configure-time check if `install -s' works.
>
> I'm not sure I'd trust such a check. I'm pretty sure it might be
> possible to construct situations in strip would succeed in stripping a
> certain simple program for a different arch
>>> "Maciej" == Maciej W Rozycki <[EMAIL PROTECTED]> writes:
Maciej> On 28 May 2001, Alexandre Duret-Lutz wrote:
[...]
>> install binaries using the system's install, and strip them
>> afterward.
[...]
Maciej> What if INSTALL_PROGRAM='$INSTALL -m111' (and you are not root)?
Ah yes, good poi
On May 28, 2001, "Maciej W. Rozycki" <[EMAIL PROTECTED]> wrote:
> I was thinking of a configure-time check if `install -s' works.
I'm not sure I'd trust such a check. I'm pretty sure it might be
possible to construct situations in strip would succeed in stripping a
certain simple program for a
On May 28, 2001, "Maciej W. Rozycki" <[EMAIL PROTECTED]> wrote:
> On 26 May 2001, Alexandre Oliva wrote:
>> > Note that I'm writing of a performance. Install-sh is a serious
>> > performance hit for non-trivial installs.
>>
>> How about only use install-sh for install-strip on cross builds?
>
On 26 May 2001, Tom Tromey wrote:
> Here in automake-land, we've long considered this the primary
> approach, with install-strip secondary. My recollection is that
> install-strip was added to the standards by RMS because he didn't want
> to add INSTALL_SCRIPT. In those days François advocated
On 28 May 2001, Alexandre Duret-Lutz wrote:
> Although i initially suggested it, there is another
> install-strip approach that we completly forgot: install
> binaries using the system's install, and strip them afterward.
I haven't forgotten, actually. I just consider it unsafe. What if
INSTA
On 26 May 2001, Alexandre Oliva wrote:
> > Note that I'm writing of a performance. Install-sh is a serious
> > performance hit for non-trivial installs.
>
> How about only use install-sh for install-strip on cross builds?
Well, that actually handles one half of the problem (yes, I do cross
b
>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On May 26, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>>> Note that I'm writing of a performance. Install-sh is a serious
>>> performance hit for non-tr
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
[...]
Tom> I agree that having install-strip work efficiently is important.
Tom> However I don't believe that it is more important than (1) getting 1.5
Tom> out in a timely way (though I don't believe this will derail it either
Tom> way), o
On May 26, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>>> Note that I'm writing of a performance. Install-sh is a serious
>>> performance hit for non-trivial installs.
Alexandre> How about only use install-sh for install-strip o
> "Maciej" == Maciej W Rozycki <[EMAIL PROTECTED]> writes:
Maciej> INSTALL_PROGRAM='${INSTALL} -s' ./configure
Maciej> make
Maciej> make install
Maciej> which I actually use for plain autoconf packages, which have
Maciej> no idea of install-strip. Still, it's more like a workaround
Maciej>
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> Note that I'm writing of a performance. Install-sh is a serious
>> performance hit for non-trivial installs.
Alexandre> How about only use install-sh for install-strip on cross builds?
I'm ok with this idea. Can it be easily
On May 24, 2001, "Maciej W. Rozycki" <[EMAIL PROTECTED]> wrote:
> On 23 May 2001, Tom Tromey wrote:
>> This is possible, but we don't recommend it. Instead we try to
>> approach cross builds the "autoconf way": we assume that configure
>> will use things like AC_CHECK_TOOL, etc.
> Note that I'
On 25 May 2001, Alexandre Duret-Lutz wrote:
> Maciej> Note that I'm writing of a performance. Install-sh is a serious
> Maciej> performance hit for non-trivial installs.
>
> Then maybe you could bypass install-strip using something like
> ./configure LDFLAGS=-s
> make
> make install
>>> "Maciej" == Maciej W Rozycki <[EMAIL PROTECTED]> writes:
Maciej> On 23 May 2001, Tom Tromey wrote:
>> This is possible, but we don't recommend it. Instead we try to
>> approach cross builds the "autoconf way": we assume that configure
>> will use things like AC_CHECK_TOOL, etc.
Maciej>
On 23 May 2001, Tom Tromey wrote:
> This is possible, but we don't recommend it. Instead we try to
> approach cross builds the "autoconf way": we assume that configure
> will use things like AC_CHECK_TOOL, etc.
Note that I'm writing of a performance. Install-sh is a serious
performance hit fo
>>>>> "Maciej" == Maciej W Rozycki <[EMAIL PROTECTED]> writes:
Maciej> I'm doing cross-compiles regularly and I've never had a
Maciej> problem with `make install-strip' using install from
Maciej> fileutils. The point is cross-t
Hi,
I see install is not used for `make install-strip' anymore. I'm not sure
if that's a good solution. Install-sh is a script and is thus much
slower. The gain is you may set the STRIPPROG environment variable. But
the gain is questionable.
I'm doing cross-compile
On May 1, 2001, Andreas Schwab <[EMAIL PROTECTED]> wrote:
> This is probably a bug in automake 1.4e.
Yep. A patch to fix is has just gone in, IIRC.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
I just thought about another minor detail
Calling `CDPATH=: && cd $_am_dirpart && pwd`/install-sh
disallows the use of install.sh.
--
Alexandre Duret-Lutz
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
Tom> I think relying on a subdir `make' invocation expanding
Tom> `INSTALL_PROGRAM' correctly is not too likely to work.
adl> I still don't and would really like to get more
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> I don't care about depend.m4, this adds only the missing changes
adl> from m4/missing.m4. Note that this also fix a bug in
adl> AC_MISSING_INSTALL_SH which was using ${ac
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
Tom> I think relying on a subdir `make' invocation expanding
Tom> `INSTALL_PROGRAM' correctly is not too likely to work.
adl> I still don't and would really like to get more feedback on this.
adl> The only workaround I can think o
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> 2001-02-25 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
adl>* header-vars.am (INSTALL_STRIP_FLAG): Remove (obsolete).
I checked this in.
Tom
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> I don't care about depend.m4, this adds only the missing changes
adl> from m4/missing.m4. Note that this also fix a bug in
adl> AC_MISSING_INSTALL_SH which was using ${ac_auxdir} instead of
adl> ${ac_aux_dir}.
Why is this nee
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> 2001-02-25 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
adl>* ChangeLog (2001-01-28): Remove entries for chunks not applied.
I'll check this in.
You don't actually need a ChangeLog entry for ChangeLog updates.
BTW I discover
> >>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> >> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
> adl> * m4/strip.m4: New file.
> adl> * m4/Makefile.am (m4data_DATA): Add strip.m4.
> adl> * m4/init.m4: Call
[...]
Tom> I think relying on a subdir `make' invocation expanding
Tom> `INSTALL_PROGRAM' correctly is not too likely to work.
adl> I don't know.
I still don't and would really like to get more feedback on
this. The only workaround I can think off is to select
the install program at run t
> >>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>
> adl> * automake.in (handle_merge_targets): In the install-strip rule,
> adl> set INSTALL_PROGRAM to INSTALL_STRIP_PROGRAM, and INSTALL_PROGRAM_ENV
> adl> to INSTALL_STRIP_PROGRAM_ENV; don't use INSTALL_STRIP_FLAG.
> adl> * progs.am (i
> >>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> >> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
> adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
> adl> * m4/strip.m4: New file.
> adl> * m4/Makefile.am (m4data_DATA): Add strip.m4.
> adl> * m4/init.m4: Call
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
adl> * m4/strip.m4: New file.
adl> * m4/Makefile.am (m4data_DATA): Add strip.m4.
adl> * m4/init.m4: Call AM_PROG_INS
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> 2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
adl>* m4/strip.m4: New file.
adl>* m4/Makefile.am (m4data_DATA): Add strip.m4.
adl>* m4/init.m4: Call AM_PROG_INSTALL_STRIP.
adl>* m4/missing.m4 (AM_AUX_DIR_E
Here is a revised patch.
2001-01-28 Alexandre Duret-Lutz <[EMAIL PROTECTED]>
* m4/strip.m4: New file.
* m4/Makefile.am (m4data_DATA): Add strip.m4.
* m4/init.m4: Call AM_PROG_INSTALL_STRIP.
* m4/missing.m4 (AM_AUX_DIR_EXPAND): New function.
(AM_MISSING_I
>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jan 23, 2001, Alexandre Duret-Lutz <[EMAIL PROTECTED]> wrote:
>> INSTALL_STRIP_PROGRAM=$$(topsrc_dir)/$(install_sh) -s
>> and then
>> install-strip:
>> $(MAKE) INSTALL_PROGRAM='$(INSTALL_STRIP_PROGRAM)' install
On Jan 23, 2001, Alexandre Duret-Lutz <[EMAIL PROTECTED]> wrote:
> INSTALL_STRIP_PROGRAM=$$(topsrc_dir)/$(install_sh) -s
> and then
> install-strip:
> $(MAKE) INSTALL_PROGRAM='$(INSTALL_STRIP_PROGRAM)' install
> So that $(topsrc_dir) gets evaluated in the sub-make. From
> the simulati
_sh) -s
#INSTALL_STRIP_PROGRAM=$$(INSTALL) -s
install:
@echo using $(INSTALL_PROGRAM)
install-strip:
$(MAKE) INSTALL_PROGRAM='$(INSTALL_STRIP_PROGRAM)' install
~/tmp % make install
using /usr/bin/install
cd a && make install
make[1]: Entering directory `/home/adl/tmp/a'
u
ing the patch I configured my package with
../configure --host=i386-mingw32msvc and did `make
install-strip' with success. If I'm correct, running ../configure
implies $srcdir = .. and thus $install_sh is relative. However
install-strip succeded! I will double check tonight to be sure;
an
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> Can someone explain me the comment before the install-strip
adl> rule: "We can't just set INSTALL_PROGRAM because that might be a
adl> relative path". This comment was added with the following
adl> ChangeLog entry:
If there is
[sorry for the previous unedited mail,
sometimes I play gnus with my feet]
>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
[...]
Alexandre> Even better! Then we can just arrange for
Alexandre> INSTALL_STRIP to set STRIPPROG and use install-sh
Alexandre> for cross install-st
>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]>
>>> writes:
Alexandre> On Jan 18, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
Alexandre> We could surely adjust install-sh so as to take a STRIP
Alexandre> variable into account, and set INSTALL_STRIP (a new
Alexandre> variable, set to th
On Jan 18, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
Alexandre> We could surely adjust install-sh so as to take a STRIP
Alexandre> variable into account, and set INSTALL_STRIP (a new
Alexandre> variable, set to the same as `$(INSTALL)' if not
Alexandre> cross-compiling, or to `STRIP=toolchain-s
Alexandre> We could surely adjust install-sh so as to take a STRIP
Alexandre> variable into account, and set INSTALL_STRIP (a new
Alexandre> variable, set to the same as `$(INSTALL)' if not
Alexandre> cross-compiling, or to `STRIP=toolchain-strip
Alexandre> $(CONFIG_SHELL) /path/to/install-sh' oth
On Jan 17, 2001, Tom Tromey <[EMAIL PROTECTED]> wrote:
adl> b) change the Makefiles to not call `install -s', but just
adl> `install' followed by a direct call to the correct strip.
> This would make sense. It is unfortunate though.
We could surely adjust install-sh so as to take a STRIP vari
>>> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
[...]
adl> b) change the Makefiles to not call `install -s', but just
adl> `install' followed by a direct call to the correct strip.
Tom> This would make sense. It is unfortu
>>>>> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
adl> Unfortunately, there is something roten with `make install-strip'
adl> in such case: `install' or `install-sh' are called with the `-s'
adl> option to strip ins
Hi all,
autoconf and automake do a great job at finding the right
tools (CC, RANLIB, etc.) to use in a package configured for
cross-compilation with --host=foobar.
Unfortunately, there is something roten with `make
install-strip' in such case: `install' or `install-sh' are
call
48 matches
Mail list logo
