On Mar 29, 2011, at 1:38 PM, TR Shaw wrote: > The problem is that the make for dynamic libraries doesn't work out of the > box so even if you compile the static version clam will link with the old > dynamic lib.
Can I "tell" clam where to get the bzip2 stuff? I know I am not using the right terminology, but will this work? 1) Compile bzip2 1.0.6 from source on a machine with the right tools and install it in /opt/local/lib 2) Compile clamd from source on the same machine with this flag: export LDFLAGS="-O3 -march=i686 -L/opt/local/lib" (Is the flag above telling clamd where to get bzip2 on the machine where clamd is running?) 3) Copy the /opt/local/lib directory containing bzip2 to each client computer 4) Install and set up the just-compiled clamd to each client computer Since I am leaving the OS-provided [and buggy] version 1.0.5 in place, won't the OS be ok? Thanks in advance for any guidance. ----------------- Russ Tyndall Wake Forest, NC _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
