Sidney Markowitz wrote: > Justin Mason wrote, On 7/1/08 7:11 AM: >> those look like warnings (hopefully). could you open a bug and attach >> a tarball of the >> temporary directory? use sa-compile --keep-tmps. > > I did that and can verify that in body_0.c there is code that would > produce those warnings if those warnings were enabled in the C > compilation. There are #line directives that would cause the warnings to > say "body_0.xs" as Doc showed, there are a number of lines of the form > while (match = Mail_SpamAssassin_CompiledRegexps_body_0_scan1 (&cursor)) > which would generate a warning in case the '='is a typo for '==' and > there is a declaration 'int i;' but no use of variable 'i'. > > So it appears that the difference is which warnings are enabled in the > compiler on our platforms using whatever command line sa-compile uses to > compile. > > -- sidney
I forgot to add things like OS and versions. OS: CentOS 5 x86_64 re2c 0.13.1 gcc (GCC) 4.1.2 perl 5.8.8 All modules are up to the current versions, also. But from what I think you're saying they're just warnings and can be ignored for the most part? -- -Doc Penguins: Do it on the ice. 8:44am up 4 days, 16:55, 17 users, load average: 0.18, 0.30, 0.37 SARE HQ http://www.rulesemporium.com/
