I'm comfortable compiling from source as long as it doesn't get too complicated with editing and dependecies.
I've been working my way up through the 32-bit versions. I was able to get 0.99 to run. I had to track down about a dozen dependencies but was finally able to get it to install. But when I run freshclam, I get the "Malformed Database" error which I understand is because the newer definition files are no readable by the older clients. So I tried the .100 version. I when through the full compile process, found the dependencies, and was able to run freshclam successfully. Then I was able to run a full system clamscan. I haven't tested the on-demand/on-access part of the product but at least .100 is looking promising. Now I'm on to the .101 version but when I "make" in the compile process, I"m getting the two errors you mentioned "-Wno-logical-op-parenthesis" and "-Wno-dangling-else". I'm in the process of researching them now. But I went ahead and ran the "make install", it seems to have installed but when I run freshclam, I'm back to the "malformed database" issue but I don't know if that is because of the errors in the "make" command. So back to testing. Sent with ProtonMail Secure Email. ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Friday, December 3rd, 2021 at 10:34 AM, Rick Cooper <rcoo...@dwford.com> wrote: > I have clam 0.103.4 running on a couple CentOS 5.11 boxes and I had to build > > A couple things and place them in non standard locations (for instance > > /opt/openssl-1.1.1g) > > There are also 4 make files that will trigger -W errors > > "-Wno-logical-op-parentheses" "-Wno-dangling-else" > > That have to be edited but I have no issues with signatures, operation or > > stability. > > I am using > > openssl-1.1.1g > > curl-7.73.0 > > zlib-1.2.11 > > If you are not comfortable building the packages needed in non standard > > locations and making sure > > /etc/ld.so.conf has the correct information, I would walk away from this > > idea. > > novpenguincne via clamav-users wrote: > > > Thanks Andrew. I am trying that now. This being an older 32-bit > > > > o/s, it has been difficult to track down the full rpm install so I've > > > > been trying to install from source. But of course that means running > > > > into dependency issues. I'll keep working on it for a bit to see if > > > > I can work through the install issues. > > > > Sent with ProtonMail Secure Email. > > > > ------- Original Message ------- > > > > > If you keep your existing SystemV scripts and build from source > > > > > > I don't expect problems with the SystemD bits. > > > > > > You probably wont get on-access scanning. > > > > > > Alternatively you could use one of your SLES15 machines as a clamd > > > > > > server > > > > > > and do your scanning with clamdscan ... > > > > > > But I would put my effort into restricting the SLES11 machine to > > > > > > local network access only (or even sneaker-net if you can work with > > > > > > that) > > > > > > before worrying about clamav. > > > > Andrew C. Aitchison Kendal, UK > > > > > > and...@aitchison.me.uk > > > > clamav-users mailing list > > > > clamav-users@lists.clamav.net > > > > https://lists.clamav.net/mailman/listinfo/clamav-users > > > > Help us build a comprehensive ClamAV guide: > > > > https://github.com/vrtadmin/clamav-faq > > > > http://www.clamav.net/contact.html#ml _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
