SA Bugzilla – Bug 2955
Won't Make in ActivePerl 5.8.2.808
Last modified: 2004-01-23 01:38:22 UTC
With MakeMaker 6.17 under ActivePerl 5.8.2.808, I get tons of errors like the following: Bareword found where operator expected at -e line 1, near ") lib" (Missing operator before lib?) Backslash found where operator expected at -e line 1, near "lib\" Backslash found where operator expected at -e line 1, near "Mail\" Backslash found where operator expected at -e line 1, near "SpamAssassin\" Bareword found where operator expected at -e line 1, near "/Mail/SpamAssassin" (Missing operator before SpamAssassin?) I suspect the makefile is not being created properly as in showing the commands, I get a list of them like this one, noting how the -DPREFIX is munged: C:\Perl\bin\perl.exe -MExtUtils::Install -e "pm_to_blib ({@ARGV}, 'blib\ lib\auto', 'C:\Perl\bin\perl.exe build/preprocessor -Mconditional -Mvars - DVERS ION="2.63" -DPREFIX=""')" lib/Mail/SpamAssassin/Dns.pm blib\lib\Mail\SpamAssassi n\Dns.pm lib/Mail/SpamAssassin/AutoWhitelist.pm blib\lib\Mail\SpamAssassin\Auto Whitelist.pm lib/Mail/SpamAssassin/BayesStore.pm blib\lib\Mail\SpamAssassin\Bay esStore.pm lib/Mail/SpamAssassin/Locker.pm blib\lib\Mail\SpamAssassin\Locker.pm lib/Mail/SpamAssassin/EncappedMIME.pm blib\lib\Mail\SpamAssassin\EncappedMIME. pm lib/Mail/SpamAssassin/Util.pm blib\lib\Mail\SpamAssassin\Util.pm lib/Mail/S pamAssassin/Conf.pm blib\lib\Mail\SpamAssassin\Conf.pm lib/Mail/SpamAssassin/Me ssage.pm blib\lib\Mail\SpamAssassin\Message.pm lib/Mail/SpamAssassin/MailingLis t.pm blib\lib\Mail\SpamAssassin\MailingList.pm lib/Mail/SpamAssassin/ArchiveIte rator.pm blib\lib\Mail\SpamAssassin\ArchiveIterator.pm lib/Mail/SpamAssassin/Cm dLearn.pm blib\lib\Mail\SpamAssassin\CmdLearn.pm lib/Mail/SpamAssassin/SHA1.pm blib\lib\Mail\SpamAssassin\SHA1.pm lib/Mail/SpamAssassin/AuditMessage.pm blib\l ib\Mail\SpamAssassin\AuditMessage.pm lib/Mail/SpamAssassin/Reporter.pm blib\lib \Mail\SpamAssassin\Reporter.pm lib/Mail/SpamAssassin/Locales.pm blib\lib\Mail\S pamAssassin\Locales.pm lib/Mail/SpamAssassin/ConfSourceSQL.pm blib\lib\Mail\Spa mAssassin\ConfSourceSQL.pm lib/Mail/SpamAssassin/Bayes.pm blib\lib\Mail\SpamAss assin\Bayes.pm lib/Mail/SpamAssassin/DBBasedAddrList.pm blib\lib\Mail\SpamAssas sin\DBBasedAddrList.pm lib/Mail/SpamAssassin/HTML.pm blib\lib\Mail\SpamAssassin \HTML.pm Anyway, it makes fine under Perl 5.8.0, so I guess more testing as to the latest version I can run where I can still make and install it is in order... I tried installing an MakeMaker 6.05, but then it simply told me it didn't know how to make anything.
This is a duplicate of bug #2808, which is resolved as a duplicate of bug #2862 because the fix for 2862 also takes care of 2808. The fix for 2862 is checked in to head. I updated my ActivePerl installation to a newer Makemaker 6.21. Could someone who has ActivePerl 5.8.2.808 with the original MakeMaker 6.17 verify that it makes ok with the current head repository? I don't have the rights to mark this as a duplicate.
thanks Sidney. *** This bug has been marked as a duplicate of 2808 ***
Created attachment 1721 [details] Makefile.PL that Works for ActivePerl 5.8.2.808 In case someone else wants to run the current released version (2.63) on Windows with ActivePerl 5.8.2, I've uploaded the modified makefile.pl. Sorry, I don't know how to create or use a patch file, so I've uploaded the whole file.
Was this already resolved? I've just installed SA 2.63 under Perl 5.8.2.808 and did not have any problems. Writing Makefile for Mail::SpamAssassin Makefile written by ExtUtils::MakeMaker 6.17
If you were installing with CYGWIN, I'm told there wasn't an issue. With ActivePerl 5.8.2.808 in native windows 2000 or XP, you couldn't install with the makefile.pl that is part of the 2.63 release. The modified makefile.pl here resolves that. There is also an entry in the FixingProblems section of the wiki that explains this.
ActivePerl is a native Windows port of Perl. This bug is only under Windows. See bug #2862 which has a more complete fix for building SpamAssassin under Windows, not just the make problem described in this bug report. That fix is already checked in to head, but I don't think it is in the 2.63 branch.