http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5508
------- Additional Comments From [EMAIL PROTECTED] 2007-06-22 07:38 -------
Downgrading re2c to version 0.12.1 works OK. re2c v0.13.x reproducibly does
not.
I understand that v0.13.x is "(as yet unreleased) development code". That's
also true of SA 3.3.x.
Might I ask, then: What /are/ the re2c version requirements, and where are they
stated?
On the mailing list, I believe I'd only found references to using "at least"
0.12.something-or-other.
In "Changes", there's "note re2c version requirements for sa-compile". As far
as I can tell, it doesn't tell me WHERE it's noted.
Digging with "grep re2c `grep -rlni re2c .`"
./.svn/text-base/Changes.svn-base:note re2c version requirements for
sa-compile
./.svn/text-base/sa-compile.raw.svn-base: "Have you got a
sufficiently-recent version of re2c?\n".
./blib/script/sa-compile: "Have you got a sufficiently-recent
version
of re2c?\n".
./sa-compile: "Have you got a sufficiently-recent version of
re2c?\n".
./sa-compile.raw: "Have you got a sufficiently-recent version
of re2c?\n".
And looking in "sa-compile" I can find only,
# scannerN() functions
if ($? >> 8 != 0) {
my $cwd = `pwd`; chop $cwd;
die "'$cmd' failed, dying!\n".
-> "Have you got a sufficiently-recent version of re2c?\n".
"see $cwd/scanner$_.re\n";
}
Or, is it obviously stated, and I have simply missed it?
As for v0.13.x of re2c, it seems from your comment that you believe it's a bug
in re2c, rather than anything in SA. I'm not qualified to verify, or disprove,
that.
Is that something you'll undertake to find/fix/communicate? Or is it left to
others?
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
