On Thu, 03 Jul 2003 08:22:12 +0200, Michael Scherer wrote:
> On Thursday 03 July 2003 00:26, R.I.P. Deaddog wrote:
>> On 2003-07-02(Wed) 17:40:24 -0400, Charles A Edwards wrote:
>> > That's fine if it works.
>> > But why not upgrade the distros libtool to 1.5?
>>
>> (gc, don't know if you can spare some time for libtool package, I
>> have virtually modified ALL patches so they do the right thing now)
>>
>> But Charles, upgrading to 1.5 can mean a lot of trouble too. Yes,
>> sooner or later we will move on, but for now, you have do these steps
>> when building stuff with libtool 1.5, if software was bundling
>> libtool 1.4:
>>
>> %{_libtoolize} -c -f
>> aclocal
>> autoconf
>
> maybe i am saying something dump, but, what about adding these steps to
> the
This would be stupid..
We are not supposed to update macros nor regenerate configure at build
time (except when patching configure.in)..
libtoolize is run to update config.* scripts which sometime don't support
new arch.. But this fails when libtool version on the compilation system
is different for the one used by tarball creator..
--
Frederic Crozat
MandrakeSoft
