unsubscribe
___
Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq
http://www.clamav.net/support/ml
Definitely for my case it is a sha256 calculation problem.
I started to compare debug output from x86 (which works ok) and this VLIW stuff
and found the following:
libclamav/dsig.c cli_versig2() fails on "if(!(salt = memchr(data, 0x01,
BLK_LEN)))" for VLIW
and difference in ctx contents (compare
It may be something platform-specific. Please open a bugzilla bug at
bugzilla.clamav.net. If you can attach the config.log files from both
0.97.8 and 0.98 then we can take a closer look from there.
Dave R.
On Sun, Sep 29, 2013 at 10:00 AM, Ari Sovijärvi wrote:
> > Note that clamav was compiled
> Note that clamav was compiled for SPARCv8 compatible processor so for me it
> looks like a byte-order problem.
> Actually it is not a SPARC, but a VLIW processor binary compatible with x86.
> At least standart byte-order check in C shows little-endian.
I have ClamAV running on a FreeBSD 8/SPARC-
UPDATE
> Hello, I tried to start a directory scan with client used
> clamav-0.97.7.tar.gz and fresh databases
> and get the following errors (actually not from stderr but using strace):
>
> LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar
> support unavailable
> LibC
Hello, I tried to start a directory scan with client used clamav-0.97.7.tar.gz
and fresh databases
and get the following errors (actually not from stderr but using strace):
LibClamAV Warning: Cannot dlopen libclamunrar_iface: file not found - unrar
support unavailable
LibClamAV Warning: ***
