https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5899
Summary: sa-compile /var/lib dir should contain perl version in
path
Product: Spamassassin
Version: SVN Trunk (Latest Devel Version)
Platform: Other
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: sa-compile
AssignedTo: [email protected]
ReportedBy: [EMAIL PROTECTED]
from Debian bug #479865:
Subject: Bug#479865: spamassassin: perl 5.10 issue with sa-compile
From: Paul Wise <pabs.debian.org>
Date: Wed, 07 May 2008 11:40:19 +0800
To: Debian Bug Tracking System <submit.bugs.debian.org>
Package: spamassassin
Version: 3.2.4-1
Severity: normal
> I couldn't get spamassassin to start after upgrading to perl
> 5.10. Srangely it works with -D enabled, but then doesn't let you stop
> it. The issue seems to be a problem with sa-compile and a symbol removed
> from perl: Perl_Tstack_sp_ptr. I was able to fix it by removing
> body_0.so and then rerunning sa-compile.
my response:
sa-compile output (including body_0.so etc.) is specific to the version of
perl it was built with. The ABI for compiled perl XS modules changed
between 5.8.x and 5.10.x. This is what caused the sa-compile output to
become unloadable once you upgraded perl.
We need to fix SpamAssassin to include part of the perl version string
("5.10" for 5.10.0, "5.8" for 5.8.x, etc.) in the pathname of the
sa-compile output to avoid this, I think.
In the meantime, deleting the /var/lib/spamassassin/compiled/ dir when
you upgrade perl, and re-running sa-compile, will avoid this.
--
Configure bugmail:
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
