Michael G Schwern wrote:

>On Mon, Mar 14, 2005 at 10:04:24AM +0000, Steve Hay wrote:
>  
>
>>NMAKE : fatal error U1071: cycle in dependency tree for target 'pm_to_blib'
>>Stop.
>>    
>>
>[...]
>Try the latest version from the repository.
>
Yep, that works for building Tk now.

However, it has some new problems of its own:  "perl Makefile.PL" and 
"nmake test" both produce these warnings:

Use of uninitialized value in concatenation (.) or string at 
lib/ExtUtils/MakeMaker.pm line 538.
Use of uninitialized value in concatenation (.) or string at 
lib/ExtUtils/MM_Unix.pm line 405.

and I also had some tests fail:

Failed Test            Stat Wstat Total Fail  Failed  List of Failed
-------------------------------------------------------------------------------
t/postamble.t             1   256     8    1  12.50%  4
t/writemakefile_args.t    2   512    16    2  12.50%  4-5
6 tests and 46 subtests skipped.
Failed 2/39 test scripts, 94.87% okay. 3/638 subtests failed, 99.53% okay.
NMAKE : fatal error U1077: 'C:\perl5\bin\perl.exe' : return code '0xff'
Stop.

I think it's all caused by a missing Revision:

6.25_10 contains:
($Revision) = q$Revision: 3933 $ =~ /Revision:\s+(\S+)/;

while the svn checkout has:
($Revision) = q$Revision$ =~ /Revision:\s+(\S+)/;

Is this just because I have a svn checkout rather than a released tarball?



------------------------------------------------
Radan Computational Ltd.

The information contained in this message and any files transmitted with it are 
confidential and intended for the addressee(s) only.  If you have received this 
message in error or there are any problems, please notify the sender 
immediately.  The unauthorized use, disclosure, copying or alteration of this 
message is strictly forbidden.  Note that any views or opinions presented in 
this email are solely those of the author and do not necessarily represent 
those of Radan Computational Ltd.  The recipient(s) of this message should 
check it and any attached files for viruses: Radan Computational will accept no 
liability for any damage caused by any virus transmitted by this email.

Reply via email to