Libtool and Support for Shared Libraries (2)

[Jeroen van Meeuwen (Kolab Systems)]

On 2012-05-29 1:25, Greg Banks wrote:
> On Mon, May 28, 2012, at 09:33 PM, Dilyan Palauzov wrote:
>> >> [...]probably using make install DESTDIR= with
>> >> libtool is either wrong or implemented/handled wrong in 
>> Automake/libtool.
>> >
>> > Well, that sucks.
>>
>> Why do not you use ./configure --prefix=$(DESTDIR), so that make
>> install DESTDIR=somewhere is not necessary?  To my understanding
>> installing in DESTDIR is used to create packages,
>
> So we now generate dozens of warnings when doing a straightforward,
> entirely normal, and unavoidable step in the packaging process?  I 
> don't
> see how that's acceptable.
>

While of course in my realm of packaging, I could use ./configure, what 
I actually use is %configure. It expands to a predefined set of standard 
configure options such as --prefix=/usr, --libdir=/usr/lib64, etc, along 
with first exporting a bunch of variables.

When the make install DESTDIR=/some/where is issued, we point it to the 
root directory of a buildroot (%{buildroot}) and expect the other 
./configure options to kick in so that everything is still finally 
placed in the correct directories (i.e.%{buildroot}etc/ for 
--sysconfdir=%{_sysconfdir}, %{buildroot}usr/lib64 for 
--libdir=%{_libdir}, etc. exec dir, libexec dir, ...) for which, if the 
prefix were to be set to the buildroot root directory, we would need to 
add the options for all the other --*dir= configure options as well.

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08