On Tue, 2008-11-04 at 15:18 -0600, Chris wrote:
> On Tuesday 04 November 2008 3:09 pm, Nathan Brink wrote:
> > Chris wrote:
> > > Is there a different version of libtool required to build 94.1 than there
> > > was to build .94?
> >
> > I had this problem too. However, I think I only had it when I ran
> > libtoolize and/or ran autoreconf. I think that ClamAV people are assuming
> > you won't run libtoolize and autoreconf when building clamav. See my bug
> > #1251 at:https://wwws.clamav.net/bugzilla/show_bug.cgi?id=1251 .
> >
> >
> > On my machine, if I remove the files m4/{lt*,libtool}.m4 before running
> > libtoolize and autoreconf, compiling works fine. I hope that works for
> > you too.
> >
> I may have been a bit unclear, I'm trying to build Mandrake 10.1 rpms. Just
> had back surgery yesterday so probably too many pain meds.
The "problem" relates to bug# 1251 as previously mentioned. In the
Mandriva rpm spec file, the macro % configure2_5xis used, which among
other things does this:
cputoolize -c .
cd .
'[' -f configure.in -o -f configure.ac ']'
libtoolize --copy --force
which means libtoolize is always called since there's a configure.in
file in the top level clamav directory. I do not know why this was not
a problem before but probably has to do with pulling in the newer
macros as mentioned in the bug report. (I'm using libtool-1.5.18.)
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
-Bill
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
