Frans,

Can you please create a ticket on https://github.com/Cisco-Talos/clamav/issues 
for the clamd test failure? Please attach the verbose output from running:
  ctest -V

Regarding make -j [n] vs ninja -- yes it's not a huge difference.  It's just a 
convenience if you're compiling a lot.  We should probably remove the ninja 
suggestion from the INSTALL.md file.
I didn't include it in 
https://docs.clamav.net/manual/Installing/Installing-from-source-Unix.html 
We do mention it here, which is good enough: 
https://docs.clamav.net/manual/Development/development-builds.html

-Micah

> -----Original Message-----
> From: clamav-users <clamav-users-boun...@lists.clamav.net> On Behalf Of
> Frans de Boer
> Sent: Sunday, July 25, 2021 11:08 AM
> To: clamav-users@lists.clamav.net
> Subject: Re: [clamav-users] ClamAV® blog: ClamAV 0.104.0 Release Candidate
> is here!
> 
> I get things compiled etc., but testing clamd keeps on failing. I tried three
> different machines/CPU's to no avail.
> 
> I use OpenSUSE Tumbleweed with newest cmake etc.
> 
> One remark: using 'make -j [n]' instead of ninja only takes less than 2 
> seconds
> longer to build things. So, the 'big speed up' is only a 'very minor speed 
> up'. Of
> course if you compile a very large amount of software every day, multiple 
> times
> a day, those less than 2 seconds do add up.
> 
> Any suggestion what data I can provide to find the cause of the failure?
> 
> Regards, Frans.
> 
> _______________________________________________
> 
> 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

Reply via email to