Date: Thu, 04 Aug 2022 20:08:34 +0900 (JST) From: Yasuhiro Kimura <yasu@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: ClamAV requiring COMPAT_FREEBSD11 Message-ID: <20220804.200834.1997957378368998820.yasu@FreeBSD.org> In-Reply-To: <8e682d62-4f73-959c-bd91-eef1c60c8202@netfence.it> References: <8e682d62-4f73-959c-bd91-eef1c60c8202@netfence.it>
next in thread | previous in thread | raw e-mail | index | archive | help
From: Andrea Venturoli <ml@netfence.it> Subject: ClamAV requiring COMPAT_FREEBSD11 Date: Thu, 4 Aug 2022 12:49:11 +0200 > > Hello. > > I build clamav-0.105.1,1 (from quarterly branch) in Poudriere and I've > always used it without problems. > > Suddenly last night freshclam started dying on a few machines: it turn > out it prints "bad system call", due to the lack of COMPAT_FREEBSD11 > in the kernel. > Strangely it's been working with those kernels for years. > > In any case, I'm trying to find a way out of this: I really wouldn't > want to install a new kernel on a remote machine, considering the > customers might be on the verge of closing for holidays, so I might > not have the chance to go and fix it in case of troubles. > OTOH I can't leave ClamAV without DB updates for weeks, so I'm > investigating if an alternative exists. > > Why this requirement? > Is there a way to recompile ClamAV in order to let freshclam work > without this kernel support? > > Thanks. > > bye > av. > Commit updating security/clamav to 0.105.1,1 isn't merged to current (2022Q3) quarterly branch. So if you really build with quarterly branch and get 0.105.1,1, it is very likely you make something wrong with building clamav package. And please provide following imformation. * Your rchitecture * Your OS version (both host and jail) * Your options setting Best Regards. --- Yasuhiro Kimura
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220804.200834.1997957378368998820.yasu>