On 06/22/2011 05:05 AM, Paul Kraus wrote: > On Tue, Jun 21, 2011 at 9:05 PM, aCaB <aca...@digitalfuture.it> wrote: >> On 06/21/11 22:54, Paul Kraus wrote: >>> I suspect that this >>> is either a unit_tests issue -or- and issue with how the static >>> executables get built. >> [...] >>> $ ./configure --disable-clamav --enable-check --enable-static >>> --disable-shared >> >> Static unrar is unlikely to work since libclamav dlopen()'s it due to >> license restrictions and incompatibilities. > > That would explain why it seems to build it shared even when I > --disable-shared. Thanks for the heads up. > >> Do you really need a static build? > > For security reasons we want the ClamAV installation to be read > only, so I build and install it in a Solaris 10 Global Zone and the > Non-Global Zones all inherit the executables (and update the > definitions there as well). Making it static is safer, as I can't > guarantee what any user or application's library search path will be. > I suppose if the code sets it's own library paths intelligently we > should be OK. > > The shared build I tried earlier went down in flames with an odd > permissions error on the bzip2 libraries. More when I am back in the > office on Thursday.
This will tell you the search path used by ClamAV to load unrar: $ grep LT_DLSEARCH_PATH clamav-config.h On my box it is: /lib:/usr/lib:/usr/local/lib:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/lib32:/usr/lib32 Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
