[clamav-users] ClamAV 0.103.0 check3_clamd.sh fails

[G.W. Haywood]

Hi there,

On Tue, 29 Sep 2020, Francis Stevens via clamav-users wrote:

> I'm trying to build 0.103.0 on a CentOS6 server and the build completes but 
> the 'make check' is giving a failure on check3_clamd.sh.  The file 
> unit_tests/check3_clamd.log contains the following but apart from the obvious 
> that the reply is the wrong size I don't know what this is telling me or what 
> I should be looking at to fix it.

Sorry I can't help much with CentOS but I'll chip in until someone on
the other side of the Pond gets up. :)

You don't mention exactly which CentOS 6 you're using.  I've seen some
other mentions of issues with CentOS 6, and one report in August 2020
which claimed that the install was (mostly) OK on 6.10 but not on 6.6.
Check the archives for what other information you can find.

Having said that I'm not sure if any of it might be relevant.  Your
'Reply has wrong size' message seems to indicate that the test code
itself is doing something wrong with paths for the unit tests.  It's
reading/writing in /test/ instead of /unit-tests/ (or vice-versa).

As a quick check I ran 'make check' again on 0.103.0-rc2 and all
seemed fine, but in .../unit_tests/test-suite.log I found

8<----------------------------------------------------------------------
*** Unit tests disabled in this build
*** Use ./configure --enable-check to enable them
8<----------------------------------------------------------------------

despite having configured as suggested there:

8<----------------------------------------------------------------------
~/clamav-0.103.0-rc2 $ head config.log 
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by ClamAV configure 0.103.0-rc2, which was
generated by GNU Autoconf 2.69.  Invocation command line was

   $ ./configure --enable-check

## --------- ##
## Platform. ##
8<----------------------------------------------------------------------

My personal take on it would be just to ignore it and install anyway,
until the code which builds and runs the tests gets fixed.

-- 

73,
Ged.