There is currently a known issue with building the ClamAV Bytecode Compiler
for Debian machines using gcc-4.7.2 and g++-4.7.2. The best way to resolve
the issue is to build the bytecode compiler with a different version of the
gcc and g++ compilers.
The bytecode compiler should be able to be built
Could you tell me the results of "make clambc-only" when running on Dedian
using the gcc-4.4 and g++-4.4?
Debian machines are known to be able to compile the ClamAV Bytecode
Compiler with gcc-4.4 and g++-4.4 so knowing the new issue with the build
could lead to additional fixes.
As for operating
Looking at the building logs, I see that running "make clambc-only" runs
fine and that the error occurs in running "make" by itself. The clamav
bytecode compiler is a project that is built on top of the LLVM, in
particular, a fairly old version of the LLVM. Outside of the sections
pertaining to the
Thank you for submitting this patch!
We will evaluate the patch for an upcoming release.
Sincerely,
Kevin Lin
On Fri, Apr 25, 2014 at 9:07 PM, Chatsiri Rattana wrote:
> Hello All,
>
>I found incorrect code on sub-project LLVMjit. It cannot built source
> code success becau
The first key thing to note is ClamAV doesn't officially support regex
signatures outside of some limited support in phishing databases (*.pdb)
and whitelist databases (*.wdb). Extra details on those signature formats
can be referenced in the phishsigs_howto.pdf in the documentation directory
of th
The best place to find the documentation to using the ClamAV API functions
can be found in the source distribution's docs directory in the
clamdoc.pdf. In the 0.98.5 source, the documentation for libclamav (section
6) starts on page 22 with the API details (section 6.3) starting on page
26. Additio
It appears that the PCRE library is correctly linking in and ClamAV is
making calls to it. The error message:
LibClamAV Error: cli_pcre_parse: PCRE compilation failed at offset 0:
unknown option bit(s) set
results directly from a failed compilation of PCRE regex which in this case
is due to an un
n't
> installed on OS X by default, so I'm compiling it as well and copying all
> the binaries & libraries etc over to the destination machines at the same
> time as copying the ClamAV binaries.
>
> Mark
>
> > On 8 Dec 2015, at 6:36 pm, Kevin Lin wrote:
27;s fixed it. Thanks so much.
>
> I still can't fathom why it would work differently on different versions
> of OS X, but it looks like you've solved the problem I'm seeing for now.
>
> Thanks again
> Mark
>
> > On 8 Dec 2015, at 8:21 pm, Kevin Lin wrot
