On 2008-12-23 00:02, Oliver Moran wrote: > 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 >
Now you're missing -lclamav again: $ gcc -Wall ex1.c -o ex1 -L/Users/oliver/clamav/lib -I/Users/oliver/ clamav/include -lclamav Or just use clamav-config: $ gcc `/Users/oliver/clamav/bin/clamav-config --cflags` ex1.c `/Users/oliver/clamav/bin/clamav-config --libs` See clamav-devel, there has recently been some discussion on using ex1.c. Also be aware that the API in 0.95 will be significantly different, so I recommend you develop your application against SVN. On 2008-12-23 00:02, Oliver Moran wrote: > 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? > I meant not to include libclamav in your source distribution, since it will eventually become out-of-date. Users can download your app's sources, and download clamav, build them both and install. If you distribute binary packages along with the sources, it is up to you if you bundle libclamav or not. On Linux you would just make your package depend on libclamav being installed, I don't know about Mac OS X. Best regards, --Edwin _______________________________________________ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
