I am getting the following error and I don't know where to look to fix it:
D:\perl_modules\Module-Build-0.35.tar\Module-Build-0.35\Module-Build-0.35>pe
rl Build.PL
Set up gcc environment - 3.4.5 (mingw-vista special r3)
Set up gcc environment - 3.4.5 (mingw-vista special r3)
Checking whether
o:ben.fy...@champsoftware.com]
Sent: Monday, September 21, 2009 1:17 PM
To: module-build@perl.org
Subject: error creating 'BUILD' script
I am getting the following error and I don't know where to look to fix it:
D:\perl_modules\Module-Build-0.35.tar\Module-Build-0.35\Module-Bu
Ben Fyvie wrote:
Here is some additional info that may be helpful to know.
We had this working on a Windows 2000 Server, it is only now that we are
experiencing the problem after migrating to a Windows Server 2003 R2 server.
This is the problem, I believe:
Perl module toolchain versions insta
. Thanks!
Ben Fyvie
-Original Message-
From: John Peacock [mailto:john.peac...@havurah-software.org]
Sent: Tuesday, September 22, 2009 10:01 AM
To: Ben Fyvie
Cc: module-build@perl.org
Subject: Re: error creating 'BUILD' script
Ben Fyvie wrote:
> Here is some additional info that
Ben Fyvie wrote:
I haven't work with Perl in quite some time. I'm simply trying to setup
svn-notify on our new server following these instructions as I did on our
old server
Run this:
perldoc -m ExtUtils::Install
and then hit the spacebar until you see something like this:
=head1 VERSION
mber 22, 2009 10:52 AM
To: Ben Fyvie
Cc: module-build@perl.org
Subject: Re: error creating 'BUILD' script
Ben Fyvie wrote:
> I haven't work with Perl in quite some time. I'm simply trying to setup
> svn-notify on our new server following these instructions as I did on
Ben Fyvie wrote:
$VERSION = '1.54_00_01'; # < dont forget to update the POD section just
above this line!
The current release on CPAN is 1.54, so if ActiveState is shipping some
non-standard package, then you need to open a ticket with them (I can't
find an already open issue, but then t
> On Tue, 22 Sep 2009 12:37:17 -0400, John Peacock
> said:
> Module::Build uses a subclass of version.pm to do all of the version
> comparisons. Because they quoted the $VERSION string, it hits the
> code which validates the formatting (which ultimately is what throws
> the erro
Andreas J. Koenig wrote:
> % perl -le 'print 100_200_300'
> 100200300
>
> I'm sure we had this before but IMO a single underscore rule violates
> the principle of least surprise.
But that's not what the module had:
perl -le "print '100_200_300'"
100_200_300
Once I determined to use an underscor
2009/9/23 John Peacock :
> Andreas J. Koenig wrote:
>> % perl -le 'print 100_200_300'
>> 100200300
>>
>> I'm sure we had this before but IMO a single underscore rule violates
>> the principle of least surprise.
>
> But that's not what the module had:
>
> perl -le "print '100_200_300'"
> 100_200_300
demerphq wrote:
Where does the "only one underscore allowed" bit come from tho?
It is a longtime convention of CPAN itself:
Modules know their associated Distribution objects. They always refer
to the most recent official release. Developers may mark their releases
as unstable development ver
2009/9/23 John Peacock :
> demerphq wrote:
>>
>> Where does the "only one underscore allowed" bit come from tho?
>
> It is a longtime convention of CPAN itself:
>
>> Modules know their associated Distribution objects. They always refer
>> to the most recent official release. Developers may mark the
demerphq wrote:
Remember the old Perl maxim of "be tolerant of what you expect and
strict with what you emit".
Are there technical reasons why this should be disallowed?
Internally, version objects are stored as an array of integers for
comparison purposes. Normally, that array is split on p
13 matches
Mail list logo
