public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] clamav: Disable llvm support.
Date: Thu, 04 Jul 2019 19:33:42 +0100	[thread overview]
Message-ID: <4435725F-F6C8-4B70-8BC8-D37F3E3D6E78@ipfire.org> (raw)
In-Reply-To: <20190704134405.28913-1-stefan.schantl@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1422 bytes --]

Thanks for doing this research. Merged.

> On 4 Jul 2019, at 14:44, Stefan Schantl <stefan.schantl(a)ipfire.org> wrote:
> 
> When enabled, LLVM provides the capability to just-in-time compile ClamAV bytecode signatures.
> Without LLVM, ClamAV uses a built-in bytecode interpreter to execute bytecode signatures.
> The mechanism is different, but the results are same and the performance overall is comparable.
> 
> At present only LLVM versions up to LLVM 3.6.2 are supported by ClamAV, and LLVM 3.6.2 is old enough
> that newer distributions no longer provide it. Therefore, the ClamAV Devs recommend using the
> --disable-llvm configure option.
> 
> Fixes #11601.
> 
> Signed-off-by: Stefan Schantl <stefan.schantl(a)ipfire.org>
> ---
> clamav/clamav.nm | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/clamav/clamav.nm b/clamav/clamav.nm
> index 9a550544e..9abe6c40e 100644
> --- a/clamav/clamav.nm
> +++ b/clamav/clamav.nm
> @@ -5,7 +5,7 @@
> 
> name       = clamav
> version    = 0.101.2
> -release    = 1
> +release    = 2
> 
> groups     = System Environment/Daemons
> url        = http://www.clamav.net
> @@ -49,6 +49,7 @@ build
> 		--with-user=clamupdate \
> 	        --with-group=clamupdate \
> 		--disable-rpath \
> +		--disable-llvm \
> 		have_cv_ipv6=yes
> 
> 	# User and group have to exist to compile the source code,
> -- 
> 2.21.0
> 


      reply	other threads:[~2019-07-04 18:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 13:44 Stefan Schantl
2019-07-04 18:33 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4435725F-F6C8-4B70-8BC8-D37F3E3D6E78@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox