Re: [Clamav-users] still fighting .95
On 2009-03-29 14:42, christian wrote: ok, i am still trying to get along with 0.95. in `make check` i see: __cut__ FAIL: check_clamd.sh PASS: check_freshclam.sh PASS: check_sigtool.sh clamscan did not detect all testfiles correctly! FAIL: check_clamscan.sh __cut__ The reason for the failure should be printed right before the line FAIL: check_clamd.sh of course, i tried with .95rc2, before: __cut__ PASS: check_clamd.sh PASS: check_freshclam.sh PASS: check_sigtool.sh PASS: check_clamscan.sh __cut__ (and, i think, it even worked with rc1, afair) Did you have 0.94.x installed on the machine you tested rc1/rc2? Do you have it installed on the machine you are testing 0.95? where can i find more information on what i am probably doing wrong? It may be bug #1491, but I can't tell unless you paste the full results from make check. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] still fighting .95
thank you, edwin, for rour speedy response! On Sun, Mar 29, 2009 at 02:58:36PM +0300, Török Edwin wrote: The reason for the failure should be printed right before the line FAIL: check_clamd.sh i don't seem to find it: __cut__ PASS: check_clamav /EXT/Packages/clamav-0.95/unit_tests/clamdtest1/../../test/clam-v2.rar: OK /EXT/Packages/clamav-0.95/unit_tests/clamdtest1/../../test/clam-v3.rar: OK *** *** clamd *** FAIL: check_clamd.sh PASS: check_freshclam.sh PASS: check_sigtool.sh clamscan did not detect all testfiles correctly! FAIL: check_clamscan.sh *** valgrind tests skipped by default, use 'make check VG=1' to activate SKIP: valgrind_tests.sh *** electric-fence not found, skipping test SKIP: efence_tests.sh *** duma tests skipped by default, use 'make check RUNDUMA=1' to activate (but don't report bugs about timeouts!) SKIP: duma_tests.sh __cut__ Did you have 0.94.x installed on the machine you tested rc1/rc2? Do you have it installed on the machine you are testing 0.95? this is a productive machine where 94.2 is running successfully, for quite some time, now. i always try to `make check` *before* uninstalling/installing... It may be bug #1491, but I can't tell unless you paste the full results from make check. gladly - i hope nobody is annoyed: __cut__ Making check in libltdl make[1]: Entering directory `/EXT/Packages/clamav-0.95/libltdl' make check-am make[2]: Entering directory `/EXT/Packages/clamav-0.95/libltdl' make[2]: Nothing to be done for `check-am'. make[2]: Leaving directory `/EXT/Packages/clamav-0.95/libltdl' make[1]: Leaving directory `/EXT/Packages/clamav-0.95/libltdl' Making check in libclamav make[1]: Entering directory `/EXT/Packages/clamav-0.95/libclamav' make check-recursive make[2]: Entering directory `/EXT/Packages/clamav-0.95/libclamav' Making check in lzma make[3]: Entering directory `/EXT/Packages/clamav-0.95/libclamav/lzma' make[3]: Nothing to be done for `check'. make[3]: Leaving directory `/EXT/Packages/clamav-0.95/libclamav/lzma' Making check in . make[3]: Entering directory `/EXT/Packages/clamav-0.95/libclamav' make[3]: Leaving directory `/EXT/Packages/clamav-0.95/libclamav' make[2]: Leaving directory `/EXT/Packages/clamav-0.95/libclamav' make[1]: Leaving directory `/EXT/Packages/clamav-0.95/libclamav' Making check in clamscan make[1]: Entering directory `/EXT/Packages/clamav-0.95/clamscan' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/clamscan' Making check in clamd make[1]: Entering directory `/EXT/Packages/clamav-0.95/clamd' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/clamd' Making check in clamdscan make[1]: Entering directory `/EXT/Packages/clamav-0.95/clamdscan' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/clamdscan' Making check in freshclam make[1]: Entering directory `/EXT/Packages/clamav-0.95/freshclam' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/freshclam' Making check in sigtool make[1]: Entering directory `/EXT/Packages/clamav-0.95/sigtool' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/sigtool' Making check in clamconf make[1]: Entering directory `/EXT/Packages/clamav-0.95/clamconf' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/clamconf' Making check in database make[1]: Entering directory `/EXT/Packages/clamav-0.95/database' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/database' Making check in docs make[1]: Entering directory `/EXT/Packages/clamav-0.95/docs' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/docs' Making check in etc make[1]: Entering directory `/EXT/Packages/clamav-0.95/etc' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/etc' Making check in clamav-milter make[1]: Entering directory `/EXT/Packages/clamav-0.95/clamav-milter' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/clamav-milter' Making check in test make[1]: Entering directory `/EXT/Packages/clamav-0.95/test' make[1]: Nothing to be done for `check'. make[1]: Leaving directory `/EXT/Packages/clamav-0.95/test' Making check in unit_tests make[1]: Entering directory `/EXT/Packages/clamav-0.95/unit_tests' make check_clamav check_clamd check_clamd.sh check_freshclam.sh check_sigtool.sh check_clamscan.sh valgrind_tests.sh efence_tests.sh duma_tests.sh make[2]: Entering directory `/EXT/Packages/clamav-0.95/unit_tests' gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DSRCDIR=\/EXT/Packages/clamav-0.95/unit_tests\ -Wall -O2 -march=nocona -mfpmath=sse -MT check_clamav-check_clamav.o -MD -MP -MF .deps/check_clamav-check_clamav.Tpo -c -o
Re: [Clamav-users] still fighting .95
On 2009-03-29 15:09, christian wrote: thank you, edwin, for rour speedy response! On Sun, Mar 29, 2009 at 02:58:36PM +0300, Török Edwin wrote: The reason for the failure should be printed right before the line FAIL: check_clamd.sh i don't seem to find it: __cut__ PASS: check_clamav /EXT/Packages/clamav-0.95/unit_tests/clamdtest1/../../test/clam-v2.rar: OK /EXT/Packages/clamav-0.95/unit_tests/clamdtest1/../../test/clam-v3.rar: OK *** *** clamd *** clam-v2.rar and clam-v3.rar should be detected as ClamAV-Test-File, and not as OK that is the failure. Did you have 0.94.x installed on the machine you tested rc1/rc2? Do you have it installed on the machine you are testing 0.95? this is a productive machine where 94.2 is running successfully, for quite some time, now. i always try to `make check` *before* uninstalling/installing... Yes, that is good practice, however in this case libtool prefers libclamunrar in /usr/lib instead of the one in the build directory. This is exactly bug #1491. Since these are the only 2 failures, you can run make install, and then run make check again. It should then pass all tests. It may be bug #1491, but I can't tell unless you paste the full results from make check. gladly - i hope nobody is annoyed: Well you could have used something like pastebin, but nevermind. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] still fighting .95
hi edwin, On Sun, Mar 29, 2009 at 03:13:39PM +0300, Török Edwin wrote: This is exactly bug #1491. ok, thank you. anyway: i would have hoped that after trying `make check` in rc1 and rc2 successfully, it wouldn't fail. if i can successfully `make check` in the last rc, but not in the release proper (other things being equal): what's the sense in trying to configure/make/make check for any rc, at all? Since these are the only 2 failures, you can run make install, and then run make check again. oh well - as soon as i succeed figuring out how to integrate the totally changed clamav-milter logic (and praying, at the same time, it won't change too radically come .96 or so)... It should then pass all tests. thank you! :-) Well you could have used something like pastebin, but nevermind. omg - something out of the irc world, i guess? i wouldn't know where to find such animal - certainly not on my machine (slack 12.1)! thanks again. regards, christian -- ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
Re: [Clamav-users] still fighting .95
On 2009-03-29 16:34, christian wrote: hi edwin, On Sun, Mar 29, 2009 at 03:13:39PM +0300, Török Edwin wrote: This is exactly bug #1491. ok, thank you. anyway: i would have hoped that after trying `make check` in rc1 and rc2 successfully, it wouldn't fail. if i can successfully `make check` in the last rc, but not in the release proper (other things being equal): what's the sense in trying to configure/make/make check for any rc, at all? Even with the -rc the wrong libclamunrar (from 0.94.2) got loaded, but the old library just worked and the problem of loading the wrong library wasn't noticed. Since these are the only 2 failures, you can run make install, and then run make check again. oh well - as soon as i succeed figuring out how to integrate the totally changed clamav-milter logic (and praying, at the same time, it won't change too radically come .96 or so)... It should then pass all tests. thank you! :-) Well you could have used something like pastebin, but nevermind. omg - something out of the irc world, i guess? i wouldn't know where to find such animal - certainly not on my machine (slack 12.1)! By pastebin I mean services like paste.debian.net, or pastebin.com, where you can paste your output, and then only send a link to it. Best regards, --Edwin ___ Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net http://www.clamav.net/support/ml
