I had given that a shot before. Still no joy. Back to something *like*
the original error:
$ gcc -Wall ex1.c -o ex1 -L/Users/oliver/clamav/lib -I/Users/oliver/
clamav/include
Undefined symbols:
"_cl_scandesc", referenced from:
_main in ccPMHetD.o
"_cl_strerror", referenced from:
_main in ccPMHetD.o
_main in ccPMHetD.o
_main in ccPMHetD.o
"_cl_free", referenced from:
_main in ccPMHetD.o
_main in ccPMHetD.o
_main in ccPMHetD.o
"_cl_build", referenced from:
_main in ccPMHetD.o
"_cl_load", referenced from:
_main in ccPMHetD.o
"_cl_retdbdir", referenced from:
_main in ccPMHetD.o
ld: symbol(s) not found
collect2: ld returned 1 exit status
Content of /Users/oliver/clamav/include is as follows:
$ cd /Users/oliver/clamav/include
$ ls
clamav.h
(The error in my originally post was got by linking ex1.c to a copy of
the libclamav directory that came in the in the clamav-0.94.2
distribution by means of #include "libclamav/clamav.h" in the source
file.)
> I'd rather not distribute libclamav bundled, since this would mean you
> would need to release a new version of your app
> every time a new libclamav is released.
I don't quite follow. Wouldn't a separately installed libclamav not go
just as stale as a bundled library over time? What's your preferred
distribution method?
Sorry to be a pest,
Oliver
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
