Re: [Clamav-users] byte code compiler configure issues
On 05/02/2010 12:49 AM, Tom Shaw wrote: At 10:52 PM +0300 5/1/10, Török Edwin wrote: Please run 'make VERBOSE=1', and paste the output. llvm[3]: Compiling version.c for Release build Thanks, please 'git pull' and try building again. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
At 10:45 AM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 12:49 AM, Tom Shaw wrote: At 10:52 PM +0300 5/1/10, Török Edwin wrote: Please run 'make VERBOSE=1', and paste the output. llvm[3]: Compiling version.c for Release build Thanks, please 'git pull' and try building again. Edwin, No joy: /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/obj/tools/opt/Release/GraphPrinters.o /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/obj/tools/opt/Release/PrintSCC.o /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/obj/tools/opt/Release/opt.o \ -lLLVMipo -lLLVMScalarOpts -lLLVMInstCombine -lLLVMInstrumentation -lLLVMTransformUtils -lLLVMipa -lLLVMAnalysis -lLLVMTarget -lLLVMMC -lLLVMAsmParser -lLLVMBitWriter -lLLVMBitReader -lLLVMCore -lLLVMSupport -lLLVMSystem -lpthread -lm Undefined symbols: llvm::Value::getUnderlyingObject(), referenced from: llvm::LoopDependenceAnalysis::analysePair(llvm::LoopDependenceAnalysis::DependencePair*) constin libLLVMAnalysis.a(LoopDependenceAnalysis.o) llvm::LoopDependenceAnalysis::analysePair(llvm::LoopDependenceAnalysis::DependencePair*) constin libLLVMAnalysis.a(LoopDependenceAnalysis.o) typeinfo for llvm::ScalarEvolution, referenced from: __ZTIN4llvm15ScalarEvolutionE$non_lazy_ptr in libLLVMScalarOpts.a(LoopDeletion.o) __ZTIN4llvm15ScalarEvolutionE$non_lazy_ptr in libLLVMAnalysis.a(LoopDependenceAnalysis.o) __ZTIN4llvm15ScalarEvolutionE$non_lazy_ptr in libLLVMScalarOpts.a(LoopRotation.o) typeinfo for llvm::LoopPass, referenced from: typeinfo for (anonymous namespace)::LoopDeletionin libLLVMScalarOpts.a(LoopDeletion.o) typeinfo for (anonymous namespace)::LoopExtractorin libLLVMipo.a(LoopExtractor.o) typeinfo for (anonymous namespace)::LCSSAin libLLVMTransformUtils.a(LCSSA.o) typeinfo for llvm::LoopDependenceAnalysisin libLLVMAnalysis.a(LoopDependenceAnalysis.o) typeinfo for (anonymous namespace)::LoopRotatein libLLVMScalarOpts.a(LoopRotation.o) typeinfo for llvm::TargetData, referenced from: __ZTIN4llvm10TargetDataE$non_lazy_ptr in libLLVMAnalysis.a(LazyValueInfo.o) typeinfo for llvm::CallGraph, referenced from: __ZTIN4llvm9CallGraphE$non_lazy_ptr in libLLVMipo.a(PruneEH.o) typeinfo for llvm::CallGraphSCCPass, referenced from: typeinfo for (anonymous namespace)::PruneEHin libLLVMipo.a(PruneEH.o) typeinfo for llvm::Inliner, referenced from: typeinfo for (anonymous namespace)::AlwaysInlinerin libLLVMipo.a(InlineAlways.o) typeinfo for (anonymous namespace)::SimpleInlinerin libLLVMipo.a(InlineSimple.o) typeinfo for llvm::LoopInfo, referenced from: __ZTIN4llvm8LoopInfoE$non_lazy_ptr in libLLVMScalarOpts.a(LoopDeletion.o) __ZTIN4llvm8LoopInfoE$non_lazy_ptr in libLLVMScalarOpts.a(LoopRotation.o) typeinfo for llvm::AliasAnalysis, referenced from: __ZTIN4llvm13AliasAnalysisE$non_lazy_ptr in libLLVMAnalysis.a(AliasSetTracker.o) typeinfo for llvm::LibCallAliasAnalysisin libLLVMAnalysis.a(LibCallAliasAnalysis.o) __ZTIN4llvm13AliasAnalysisE$non_lazy_ptr in libLLVMAnalysis.a(LoopDependenceAnalysis.o) ld: symbol(s) not found collect2: ld returned 1 exit status make[2]: *** [/Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/obj/Release/bin/opt] Error 1 make[1]: *** [opt/.makeall] Error 2 make: *** [all] Error 1 ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
On 05/02/2010 04:44 PM, Tom Shaw wrote: At 10:45 AM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 12:49 AM, Tom Shaw wrote: At 10:52 PM +0300 5/1/10, Török Edwin wrote: Please run 'make VERBOSE=1', and paste the output. llvm[3]: Compiling version.c for Release build Thanks, please 'git pull' and try building again. Edwin, No joy: Use 'make clambc-only', that is what the manual says ;) Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
At 4:46 PM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 04:44 PM, Tom Shaw wrote: At 10:45 AM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 12:49 AM, Tom Shaw wrote: At 10:52 PM +0300 5/1/10, Török Edwin wrote: Please run 'make VERBOSE=1', and paste the output. llvm[3]: Compiling version.c for Release build Thanks, please 'git pull' and try building again. Edwin, No joy: Use 'make clambc-only', that is what the manual says ;) I did and got the error and then made with make VERBOSE=1 like you asked the last time ;-) I have made again like you asked (which isn't what is in the docs in para 1.3.2 and 1.4 ) Still no joy: /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/llvm/projects/clamdriver/clamdriver/driver.cpp: In function 'int CompileSubprocess(const char**, int, llvm::sys::Path, bool, bool, llvm::sys::Path)': /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/llvm/projects/clamdriver/clamdriver/driver.cpp:453: error: 'class std::vectorchar*, std::allocatorchar* ' has no member named 'data' make[3]: *** [/Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/obj/projects/clamdriver/clamdriver/Release/driver.o] Error 1 make[2]: *** [all] Error 1 make[1]: *** [all] Error 1 make: *** [clambc-only] Error 2 -- Tom Shaw - Chief Engineer, OITC tshaw at oitc.com, http://www.oitc.com/ local wx: http://www.oitc.com/weather US Phone Numbers: 321-984-3714, 321-729-6258(fax), 321-258-2475 (cell/voice mail,pager) US skypeline: 321-622-9098 Text Paging: http://www.oitc.com/Pager/sendmessage.html AIM/iChat: trs...@mac.com Skype: trshaw Fish more and Live longer To err is human. To purr, feline ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
On 05/02/2010 05:33 PM, Tom Shaw wrote: At 4:46 PM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 04:44 PM, Tom Shaw wrote: At 10:45 AM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 12:49 AM, Tom Shaw wrote: At 10:52 PM +0300 5/1/10, Török Edwin wrote: Please run 'make VERBOSE=1', and paste the output. llvm[3]: Compiling version.c for Release build Thanks, please 'git pull' and try building again. Edwin, No joy: Use 'make clambc-only', that is what the manual says ;) I did and got the error and then made with make VERBOSE=1 like you asked the last time ;-) I have made again like you asked (which isn't what is in the docs in para 1.3.2 and 1.4 ) Still no joy: /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/llvm/projects/clamdriver/clamdriver/driver.cpp: In function 'int CompileSubprocess(const char**, int, llvm::sys::Path, bool, bool, llvm::sys::Path)': /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/llvm/projects/clamdriver/clamdriver/driver.cpp:453: error: 'class std::vectorchar*, std::allocatorchar* ' has no member named 'data' We're getting closer. This is one more case of .data() usage, I just commited something to fix it. Please try now. BTW what platform are you doing this on? Mac OS X 10.6? Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
At 6:07 PM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 05:33 PM, Tom Shaw wrote: At 4:46 PM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 04:44 PM, Tom Shaw wrote: At 10:45 AM +0300 5/2/10, Török Edwin wrote: On 05/02/2010 12:49 AM, Tom Shaw wrote: At 10:52 PM +0300 5/1/10, Török Edwin wrote: Please run 'make VERBOSE=1', and paste the output. llvm[3]: Compiling version.c for Release build Thanks, please 'git pull' and try building again. Edwin, No joy: Use 'make clambc-only', that is what the manual says ;) I did and got the error and then made with make VERBOSE=1 like you asked the last time ;-) I have made again like you asked (which isn't what is in the docs in para 1.3.2 and 1.4 ) Still no joy: /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/llvm/projects/clamdriver/clamdriver/driver.cpp: In function 'int CompileSubprocess(const char**, int, llvm::sys::Path, bool, bool, llvm::sys::Path)': /Users/tshaw/Sites/clamav/clamav-bytecode-compiler.old/clamav-bytecode-compiler/llvm/projects/clamdriver/clamdriver/driver.cpp:453: error: 'class std::vectorchar*, std::allocatorchar* ' has no member named 'data' We're getting closer. This is one more case of .data() usage, I just commited something to fix it. Please try now. BTW what platform are you doing this on? Mac OS X 10.6? Trying now let you know in about 10 10.5.8 right now. 10.6 after we get this working Tom ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
At 6:07 PM +0300 5/2/10, Török Edwin wrote: We're getting closer. T Thanks, Edwin. That worked. Installed and tried to get version but got: $ /usr/local/clamav/bin/clambc-compiler -v clang -cc1 version 1.1 based upon llvm 2.7 hosted on i386-apple-darwin9 re2c: error: cannot re-open stdin error: re2c command failed with exit code 1 (use -v to see invocation) Compiler exited with code 1! Going to now look for an example to insure its working correctly. Thanks again. Tom PS What the heck is the .data() function? ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
On 05/02/2010 06:21 PM, Tom Shaw wrote: At 6:07 PM +0300 5/2/10, Török Edwin wrote: We're getting closer. T Thanks, Edwin. That worked. Installed and tried to get version but got: $ /usr/local/clamav/bin/clambc-compiler -v Please use --version. clang -cc1 version 1.1 based upon llvm 2.7 hosted on i386-apple-darwin9 re2c: error: cannot re-open stdin error: re2c command failed with exit code 1 (use -v to see invocation) This happens because there was no input specified, I'll fix it some time. Compiler exited with code 1! Going to now look for an example to insure its working correctly. Thanks again. Tom PS What the heck is the .data() function? std::vectorint A; A.data() ^ this returns a pointer to the beginning of memory that stores the data for the vector. It is the same as A[0]. My gcc (4.4, Linux) has .data(), yours doesn't. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Resources for integrating with spamassassin+amavisd
Hi, Why are some of the databases duplicated in the clamav root dir and also in the unofficial-dbs/ss-dbs directory, such as winnow_malware.hdb? The rsync protocol only downloads the changes between the local and remote files, so the local file much be available comparison. The unofficial/ss-dbs is also the working directory where the database's GPG signature and integrity testing is done before rsyncing the files into the ClamAV production directory. By this time you must think I'm dumb or completely new at this. I'd like to think I'm just more inquisitive and going beyond just the home use. Time for some more coffee for me :-) It sounds like the real reason for is duplicates is for the integrity check, because rsync doesn't otherwise need two local copies. Also for moving them all into place into production at once? Is there support that I'm somehow missing for alerting an administrator that there was a problem when it actually happens, and not through just a daily report? How can I verify that clamd is actually using the full set of databases I've downloaded? Thanks again, Alex ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Resources for integrating with spamassassin+amavisd
On 5/2/2010 9:59 AM, Alex wrote: Hi, Why are some of the databases duplicated in the clamav root dir and also in the unofficial-dbs/ss-dbs directory, such as winnow_malware.hdb? The rsync protocol only downloads the changes between the local and remote files, so the local file much be available comparison. The unofficial/ss-dbs is also the working directory where the database's GPG signature and integrity testing is done before rsyncing the files into the ClamAV production directory. By this time you must think I'm dumb or completely new at this. I'd like to think I'm just more inquisitive and going beyond just the home use. Time for some more coffee for me :-) It sounds like the real reason for is duplicates is for the integrity check, because rsync doesn't otherwise need two local copies. Also for moving them all into place into production at once? Not just integrity testing, but first GPG signature tested in order to confirm that the files have not been compromised in any way. After the script is run, each database that has been updated is GPG signature tested, then ClamAV integrity tested, and then rsynced into the the ClamAV production directory. You do not want to place any database into the production directory until it have been tested, thus the creation and use of the working directories (/usr/unofficial-dbs/*) by the script. The script stops and reports/logs any failure along the way so that a corrupted or compromised database cannot end up in production use. Is there support that I'm somehow missing for alerting an administrator that there was a problem when it actually happens, and not through just a daily report? The only error reporting the script does is via email after each script run and logging to a log file, depending on how the user has configured the script to run. How can I verify that clamd is actually using the full set of databases I've downloaded? Any database that shows up in the ClamAV production directory is used by ClamAV/ClamD - ls /path/to/clamav will show you what database are being used. Bill ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
On 5/2/10 8:14 AM, Tom Shaw wrote: Trying now let you know in about 10 10.5.8 right now. 10.6 after we get this working Tom I was able to compile .96 in Snow Leopard with no modification. dp ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
On 05/02/2010 10:27 PM, Dennis Peterson wrote: On 5/2/10 8:14 AM, Tom Shaw wrote: Trying now let you know in about 10 10.5.8 right now. 10.6 after we get this working Tom I was able to compile .96 in Snow Leopard with no modification. He was having trouble compiling the ClamAV bytecode compiler, not ClamAV itself. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Resources for integrating with spamassassin+amavisd
On 5/2/10 9:59 AM, Alex wrote: Hi, Why are some of the databases duplicated in the clamav root dir and also in the unofficial-dbs/ss-dbs directory, such as winnow_malware.hdb? The rsync protocol only downloads the changes between the local and remote files, so the local file much be available comparison. The unofficial/ss-dbs is also the working directory where the database's GPG signature and integrity testing is done before rsyncing the files into the ClamAV production directory. By this time you must think I'm dumb or completely new at this. I'd like to think I'm just more inquisitive and going beyond just the home use. Time for some more coffee for me :-) It sounds like the real reason for is duplicates is for the integrity check, because rsync doesn't otherwise need two local copies. Also for moving them all into place into production at once? Rsync is able to transfer only the differences between two files provided a version of the file being transferred exists on the source and the destination. In addition, rsync will not transfer anything if it determines there are no changes between the two files. This saves bandwidth for the mirrors. This transfer economy requires the client maintain unmodified copies of the files in the target directory so rsync can make these comparisons. (A bit more to know: This also works best if the files are unsorted between versions. For a trivial example, a syslog file that has grown over time. Rsync will skip over the parts found in both files very quickly and transfer only those parts found in newer version. If the files have been sorted rsync has to examine and reconstruct the entire file.) The above is the reason for having a working area for rsync. A reason for keeping a separate area for clamd is because clamd will die if a corrupt file is found in the clamd working area. A corrupt file could include a file that is being copied into the working area but is not yet complete (non-atomic copy/move). As clamd does check the working area from time to time the chance exists that this scan can occur at a time a file is being placed in the working area. It is a good practice to minimize file activity in the clamd working area. As another matter of good practice I only use rsync to place signatures in the clamd working area because rsync writes to a hidden file until the transfer is complete at which time that file is renamed. As such it appears suddenly and so does not cause clamd any problems. This works for local file systems as well as NAS/NFS/FUSE/CIFS file systems. dp ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] byte code compiler configure issues
At 12:27 PM -0700 5/2/10, Dennis Peterson wrote: On 5/2/10 8:14 AM, Tom Shaw wrote: Trying now let you know in about 10 10.5.8 right now. 10.6 after we get this working Tom I was able to compile .96 in Snow Leopard with no modification. Thanks Dennis. I had no problems for ClamAV (did have a temp issue when not compiling for machine specific eg patching for PPC and patching universal compile) Here I was trying to get the bytecode compiler up and running. Tom ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] Upgrading System for latest ClamAV version
On Fri, Apr 16, 2010 at 06:36:51AM -0400, Jerry (clamav.u...@seibercom.net) wrote: Or, to put it in simpler terms, It's better to light a candle than curse the darkness. THAT is not a simple term ;-) It's better to light a (someones) candle than (to let them) curse the darkness. Considering the reactions of some participants of the previous threads that initiated this thread a lot of people do not understand this proverb, that human kind would be better off and the reason for mailing lists. BTW, some trivia: this is one of the proverbs of wikipedia. Jobst -- f u cn rd ths, u cn gt a gd jb n cmptr prgmmng. [Anon] | |0| | Jobst Schmalenbach, jo...@barrett.com.au, General Manager | | |0| Barrett Consulting Group P/L The Meditation Room P/L |0|0|0| +61 3 9532 7677, POBox 277, Caulfield South, 3162, Australia ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
