On 2009-02-20 03:13, Stephen Gran wrote:
> Now that I've been doing some looking, I see that there is also a
> bundled -ltdl in the source tree. I'm not aware of any license issues
> with libtool (although as it's an FSF project, I wouldn't be surprised
> to see it move to v3 in the future). Is this just a convenience copy,
> or is because of a license problem I'm unaware of?
>
> If it's just a convenience copy, can we give it the same treatment, and
> preferentially use the system copy? It'll probably mean patching the
> version of the ltdl m4 that you have in favor of something that doesn't
> produce totally broken make targets when you try to get it to use the
> system libtool.
>
> Currently, if you pass --with-ltdl-dir=/usr/lib, it add -L/usr/lib as
> a preprequisite, and if you pass --with-ltdl-dir=/usr/lib/libltdl.la,
> configure goes off and looks for /usr/lib/libltdl.la/libltdl.la and
> doesn't find it and exits.
>
It already picks the system ltdl, *IF* you have libltdl7-dev installed
(which is currently in experimental, waiting to be uploaded in sid).
It won't work with an older ltdl, and I don't think it would be wise to
downgrade libtool.
ldd clamscan/.libs/clamscan
linux-vdso.so.1 => (0x00007fff0c5fe000)
libclamav.so.5 => /usr/local/lib/libclamav.so.5 (0x0000003ed4200000)
libltdl.so.7 => /usr/lib/libltdl.so.7 (0x00007f78041a9000)
libbz2.so.1.0 => /lib/libbz2.so.1.0 (0x0000003ee7800000)
libz.so.1 => /usr/lib/libz.so.1 (0x0000003ed6000000)
libdl.so.2 => /lib/libdl.so.2 (0x00007f7803fa5000)
libpthread.so.0 => /lib/libpthread.so.0 (0x00007f7803d8a000)
libgcc_s.so.1 => /lib/libgcc_s.so.1 (0x00007f7803b73000)
libc.so.6 => /lib/libc.so.6 (0x00007f7803820000)
/lib64/ld-linux-x86-64.so.2 (0x00007f78043b2000
Best regards,
--Edwin
_______________________________________________
http://lurker.clamav.net/list/clamav-devel.html
Please submit your patches to our Bugzilla: http://bugs.clamav.net
