On Wed, 2008-11-05 at 13:43 +0100, aCaB wrote:
> Bill Randle wrote:
> > My workaround was to add the following to the spec file:
> > # hack to prevent libtoolize from being called. Since we don't patch
> > # the configure.in file, there's no need to re-configure.
> > mv configure.in configure.in.nu
>
> Hi all,
> Just a FYI, you can call libtoolize (or autoreconf) just don't use the
> --force option.
Good reminder for package scripts that call libtoolize directly. In
this case, it's inside a vendor system macro file that I didn't want
to edit as you never know when it might get modified on an upgrade.
-Bill
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
