SpamAssassin's sa-compiles fails after upgrading to 12.10
Donkey Hottie
donkey at fredriksson.dy.fi
Sun Oct 21 11:41:36 UTC 2012
Error occurs:
# sa-compile
Oct 21 14:34:24.429 [15165] info: generic: base extraction starting.
this can take a while...
Oct 21 14:34:24.429 [15165] info: generic: extracting from rules of type
body_0
100%
[============================================================================================================]
744.56 rules/sec 00m01s DONE
100%
[============================================================================================================]
178.04 bases/sec 00m15s DONE
Oct 21 14:34:41.143 [15165] info: body_0: 1190 base strings extracted in
17 seconds
cd /tmp/.spamassassin15165gikfcutmp
cd Mail-SpamAssassin-CompiledRegexps-body_0
re2c -i -b -o scanner1.c scanner1.re
re2c -i -b -o scanner2.c scanner2.re
re2c -i -b -o scanner3.c scanner3.re
re2c -i -b -o scanner4.c scanner4.re
re2c -i -b -o scanner5.c scanner5.re
re2c -i -b -o scanner6.c scanner6.re
/usr/bin/perl Makefile.PL
PREFIX=/tmp/.spamassassin15165gikfcutmp/ignored
INSTALLSITEARCH=/var/lib/spamassassin/compiled/5.014/3.003002
Only one of PREFIX or INSTALL_BASE can be given. Not both.
command failed: exit 255
While googlin, I got an advice:
PREFIX vs INSTALL_BASE from Module::Build::Cookbook
The behavior of PREFIX is complicated and depends closely on
how your Perl is configured. The resulting installation
locations will vary from machine to machine and even
different installations of Perl on the same machine. Because
of this, its difficult to document where prefix will place
your modules.
In contrast, INSTALL_BASE has predictable, easy to explain
installation locations. Now that Module::Build and MakeMaker
both have INSTALL_BASE there is little reason to use PREFIX
other than to preserve your existing installation locations.
If you are starting a fresh Perl installation we encourage
you to use INSTALL_BASE. If you have an existing installation
installed via PREFIX, consider moving it to an installation
structure matching INSTALL_BASE and using that instead.
I tried to add INSTALL_BASE='' sa-compile, but not helped. INSTALL_BASE
is not normal environ value, it is added by some Perl module on the way?
sa-compile apparently want to compile to some tmp location first, and
move the targets to correct location after success. This seems to break
some Debian originated stuff? But everting worked fine in 12.04.
Any ideas?
--
You are not dead yet. But watch for further reports.
More information about the ubuntu-users
mailing list