From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/clamav: needs dynamic library
Date: Wed, 23 Sep 2020 20:51:02 +0200 [thread overview]
Message-ID: <20200923205102.4bfbe959@windsurf> (raw)
In-Reply-To: <20200923175436.71450-1-bernd.kuhls@t-online.de>
On Wed, 23 Sep 2020 19:54:36 +0200
Bernd Kuhls <bernd.kuhls@t-online.de> wrote:
> Upstream commit
> https://github.com/Cisco-Talos/clamav-devel/commit/9e20cdf6eaf545a66f55ce5ba85ef9a98dad3648
> added dlopen() to others.c
> https://github.com/Cisco-Talos/clamav-devel/blob/dev/0.104/libclamav/others.c#L199
>
> "libclamav used to build in multiple stages where an earlier stage is
> a static library containing utils required by the "shared" code.
> Linking clamdscan and clamdtop with this libclamav utils static lib
> allowed these two apps to function without libclamav. While this is
> nice in theory, the practical gains are minimal and it complicates
> the build system. As such, the autotools and CMake tooling was
> simplified for improved maintainability and this feature was thrown
> out. clamdtop and clamdscan now require libclamav to function."
>
> Fixes:
> http://autobuild.buildroot.net/results/e27/e276894781e3e37fbc03a0745738c61541e0a211/
> http://autobuild.buildroot.net/results/552/552ee8d9e44152c9d7e315a5491542771264d466/
> http://autobuild.buildroot.net/results/fde/fde4af47542f0eb0bd57b172c99bd086eb566b76/
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/clamav/Config.in | 6 +++---
> package/clamav/clamav.mk | 3 ---
> 2 files changed, 3 insertions(+), 6 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-09-23 18:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-23 17:54 [Buildroot] [PATCH 1/1] package/clamav: needs dynamic library Bernd Kuhls
2020-09-23 18:51 ` Thomas Petazzoni [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=20200923205102.4bfbe959@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.