Mail-ClamAV-0.17 out

David Lee t.d.lee at DURHAM.AC.UK
Fri Mar 11 10:35:05 GMT 2005

On Thu, 10 Mar 2005, Devon Harding wrote:

> I get this error:
> Manifying blib/man3/Mail::ClamAV.3pm
>  /usr/bin/make  -- OK
> Running make test
> PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e"
> "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t
> t/Mail-ClamAV....NOK 1#     Failed test (t/Mail-ClamAV.t at line 9)
> #     Tried to use 'Mail::ClamAV'.
> #     Error:  Had problems bootstrapping Inline module 'Mail::ClamAV'
> #
> # Can't load '/root/.cpan/build/Mail-ClamAV-0.17/blib/arch/auto/Mail/ClamAV/'
> for module Mail::ClamAV: /usr/lib/ symbol __fprintf_chk,
> version GLIBC_2.3.4 not defined in file with link time
> reference at /usr/lib/perl5/5.8.3/i386-linux-thread-multi/
> line 229.
> #  at /usr/lib/perl5/site_perl/5.8.3/ line 500
> [...]

This looks like some interaction in your environment, rather than a fault
within Mail::ClamAV .

That "Can't load ... [...]/blib/arch/auto/Mail/ClamAV/" is the
fundamental thing for you to address.  And there is a good chance that the
subsequent errors should magically disappear after that.

cd to the working directory: /root/.cpan/build/Mail-ClamAV-0.17 .

See what dynamic libraries are required, which of them successfully
resolve and which fail to resolve.  Do:
    ldd ./blib/arch/auto/Mail/ClamAV/

whose output ought to be several lines of the form: =>  /path/to/somewhere/ => /path/to/elsewhere/

My guess is that that at least one of these "/path/..." things will give
some sort of "not found" message.

The rest is up to you, for your machine in your environment.  But the
strategy is to find the location of the "libXYZ.[...]" that "ldd" had
failed to find, then to tickle things to make it work.  This might involve
editing the "" (warning! it gets recreated afresh after each
"perl Makefile.PL").  Or it might mean adjusting your "/etc/"
directory (care! mistakes here could harm your system).

(I've had to dabble myself in this area.  In my case, the "ldd" failure
highlighted ", because our environment has it in an unusual
location.  In your case, it is probably a different library whose perhaps
unusual location underlies the problem.  Might you have two versions of a
library in different locations?  Does your C compiler build with one
version, but your system "/etc/" refer to different run-time

Hope that helps.


:  David Lee                                I.T. Service          :
:  Senior Systems Programmer                Computer Centre       :
:                                           University of Durham  :
:            South Road            :
:                                           Durham                :
:  Phone: +44 191 334 2752                  U.K.                  :

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ ( and
the archives (

Support MailScanner development - buy the book off the website!

More information about the MailScanner mailing list