Another Windows related question.... I (think I) successfully compiled my ruleset into native code. I used a XP box with Visual C++ 6, re2c-0.13.5 and SpamAssassin 3.3.1. sa-compile ran through but reported an error excuting the makefile. The prefix parameter, MakeMaker used to create the Makefile was a bit odd (Makefile.PL PREFIX=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\.spamassassin1296AZKswUtmp/ignored INSTALLSITEARCH=C:\Perl\site/var/spamassassin/compiled/5.008/3.003001) so I adjusted it and ran make again. This time no errors or warnings were reported, so I ran nmake install.
I copied the compiled ruleset to a test box with W2k3 and activated Rule2XSBody. After starting spamd, I saw the following line in logfile (at this point, I already had a 'yeehaw!' in mind...): info: zoom: able to use 1101/1101 'body_0' compiled rules (100%) So I started some stress tests and let spamd processing a few hunded mails to see if scanning time dropped noticeable: Average with Rule2XSBody activated: 6.93 seconds. Average without Rule2XSBody activated: 5.78 seconds. So, did I miss anything (do I have to disable the regular ruleset or so?) or is it a Windows related problem? Daniel -- View this message in context: http://old.nabble.com/sa-compile-has-no-effect-%28under-Windows.......%29-tp29304248p29304248.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
