Hello,
  Has anyone successfully compiled (version 70 - stable) on a SuSE 9 x86_64 architecture or any x86_64 distrobution architecture for that matter?  Quoted from the ClamAV site:
 
"Clam AntiVirus is prepared for the installation on the following operating systems / architectures (tested platforms in brackets):
GNU/Linux - all versions and platforms........"
 
I'm trying to compile after running the config script (with no errors that I could see) and I get this at the end after running make:
 
*** Warning: linker path does not have real file for library -lgmp.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libgmp and none of the candidates passed a file format test
*** using a file magic. Last file checked: /lib/libz.so.1.1.4
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.
gcc -shared  matcher.lo md5.lo others.lo readdb.lo cvd.lo dsig.lo str.lo scanners.lo unrarlib.lo zzip-dir.lo zzip-err.lo zzip-file.lo zzip-info.lo zzip-io.lo zzip-stat.lo zzip-zip.lo strc.lo blob.lo mbox.lo message.lo strrcpy.lo table.lo text.lo ole2_extract.lo vba_extract.lo  -lz /usr/lib/libbz2.so -lpthread  -Wl,-soname -Wl,libclamav.so.1 -o .libs/libclamav.so.1.0.3
/usr/lib/libbz2.so: could not read symbols: Invalid operation
collect2: ld returned 1 exit status
make[2]: *** [libclamav.la] Error 1
make[2]: Leaving directory `/home/natedog/Downloads/ClamAV/clamav-0.70-rc/libclamav'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/natedog/Downloads/ClamAV/clamav-0.70-rc'
make: *** [all] Error 2
So........I know that most of the libraries are in directories specific to the 64 bit platform like /usr/lib64 etc etc.  So neways.......my question is........is there a way to work around this....maybe a soft link or something?  Or am I just missing a normal library that should be there and has nothing to do with the 64 bit architecture?
 
--
Nathan Peters

Reply via email to