Problems with Clam-0.93.3-SA-3.2.5 package on Fedora Core 4

[Ian]

Hi,

I wanted to remove f-prot on one of our old machines and install Julian's Clam-
Spamassassin package but ran into some serious problems.  I managed to solve all these 
with the help of the archives and a bit of googling and though it might be useful for 
someone else.

First of all I know Fedora Core 4 is old and we will ditch it in favour of CentOS in the future 
but I didn't realize it existed in some sort of limbo between supported officially and 
supported unofficially (dag etc).  I couldn't seem to find any recent RPMs for Clamav (I 
wanted to use clamd in MailScanner) so I decided to go down the easier clamavmodule 
route.

The install of Clam-0.93.3-SA-3.2.5 seems to go ok until I ran freshclam and it reported 
that I had clamav 0.91 installed (this was already on the machine) instead of the just 
installed 0.93.

I then noticed that I was getting the error:

	None of the files matched by the "Monitors For ClamAV Updates" patterns exist! 

in the maillog so I stopped mailscanner and set Virus Scanners = none to get mail flowing 
again - after warning the users of lack of virus scanning of course ;)

A search of the archives led me to upgrade MailScanner to the latest version to get the 
right settings.

Except this didn't work.

I then decide to re-install clamav from source.

During the ./configure I got the error:

	configure: error: your compiler has gcc PR28045 bug, use a different compiler

which probably explains why Julian's package didn't work. (I still have the config.log if you 
need it).

The workaround for this is to add the flag --disable-gcc-vcheck except there is also a bug 
in this (https://wwws.clamav.net/bugzilla/show_bug.cgi?id=684) so the real workaround is 
to use:

	./configure CFLAGS="-O0"

to disable all compiler optimisations.  Yes I know I should update gcc but I have now 
decided this machine isn't going to last too long now :)

After getting clamav installed properly and configuring clamd all is working ok.  I had to do 
a ldconfig and fix the clamd.conf file to get it working though.

All this because I though updating f-prot from v4 to v6 would be a pain!

Regards

Ian
--