[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Why main Makefile don't use INSTALL_PROGRAM, only INSTALL? It causes installed binaries to be not stripped.

From: Ben Reser <ben_at_reser.org>
Date: Tue, 18 Sep 2012 22:57:23 -0700

On Fri, Sep 14, 2012 at 3:12 PM, Daniel Shahaf <d.s_at_daniel.shahaf.name> wrote:
> Forwarding to dev@
>
> Lev Serebryakov wrote on Fri, Sep 14, 2012 at 18:21:44 +0400:
>> Hello, Users.
>>
>> Now Makefile.in contains:
>>
>> INSTALL = @INSTALL@
>> ...
>> INSTALL_BIN = $(LIBTOOL) --mode=install $(INSTALL)
>>
>> And after configure it is expanded to:
>>
>> INSTALL = /usr/bin/install -c -o root -g wheel
>> ...
>> INSTALL_BIN = $(LIBTOOL) --mode=install $(INSTALL)
>>
>> It means, that all binaries are installed un-stripped. It is huge
>> amount of unneeded (unless --enable-debug is provided) information,
>> especially for static build. In case of dynamic build, all shared
>> libraries are unstripped too.
>>
>> `configure' script defines INSTLAL_PROGRAM with additional `-m 555
>> -s' options, but it is not used.
>>
>> Why is it done in such way? Could it be changed?
>>
>> Yes, I've search mailing list this time without any relevant results.
>
> I don't recall many discussions about stripped/unstripped binaries in
> the few years I'm following this list.
>
> If you don't hear any objections, I'd suggest the best way to further
> the matter would be to send a patch.

+1 to fixing this. It's clearly wrong.
Received on 2012-09-19 07:58:05 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.