Failure upgrading clamav

[graziosi.angelo@…]

Just a few minutes ago:

$ sudo port outdated
The following installed ports are outdated:
clamav                         0.98.4_1 < 0.98.5_0
gcc49                          4.9.1_1 < 4.9.2_0
libffi                         3.1_4 < 3.2.1_0
libgcc                         4.9.1_1 < 4.9.2_0

$ sudo port upgrade outdated
--->  Computing dependencies for clamav
--->  Fetching archive for clamav
--->  Attempting to fetch clamav-0.98.5_0.darwin_14.x86_64.tbz2 from http://lil.fr.packages.macports.org/clamav
--->  Attempting to fetch clamav-0.98.5_0.darwin_14.x86_64.tbz2 from http://nue.de.packages.macports.org/macports/packages/clamav
--->  Attempting to fetch clamav-0.98.5_0.darwin_14.x86_64.tbz2 from http://mse.uk.packages.macports.org/sites/packages.macports.org/clamav
--->  Fetching distfiles for clamav
--->  Attempting to fetch clamav-0.98.5.tar.gz from http://garr.dl.sourceforge.net/clamav
--->  Verifying checksums for clamav
--->  Extracting clamav
--->  Applying patches to clamav
--->  Configuring clamav
--->  Building clamav
Error: org.macports.build for port clamav returned: command execution failed
Please see the log file for port clamav for details:
    /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sysutils_clamav/clamav/main.log
Error: Unable to upgrade port: 1
To report a bug, follow the instructions in the guide:
    http://guide.macports.org/#project.tickets

main.log attached

[captainproton1971 (Captain Proton)]

Cc Me!

[gnw3]

clamav builds seem to use headers files from the currently installed version rather that from the new version. Try deactivating clamav before building from source to ensure that the new headers are used.

[danielluke (Daniel J. Luke)]

Replying to gnwiii@…:

clamav builds seem to use headers files from the currently installed version rather that from the new version. Try deactivating clamav before building from source to ensure that the new headers are used.

Yep - I replicated this problem this morning (when trac was down) and can confirm that deactivating first is a good workaround. (trace mode should work too, but I didn't test it).

[ryandesign (Ryan Carsten Schmidt)]

The attached diff works around the problem, until a better solution (e.g. reordering the -I flags) can be found.

[danielluke (Daniel J. Luke)]

thanks Ryan, r128380

[danielluke (Daniel J. Luke)]

Note that upstream's install instructions say to uninstall clamav before building/installing a new clamav - so even if we get this fixed and get them to include the fix, it's likely that the problem will return.

Here's to hoping we get trace mode working to the point where it can be always running by default :)

[danielluke (Daniel J. Luke)]

build fixed in r128386, reported upstream ​https://bugzilla.clamav.net/show_bug.cgi?id=11194