Skip Menu |

This queue is for tickets about the version CPAN distribution.

Report information
The Basics
Id: 45396
Status: rejected
Priority: 0/
Queue: version

People
Owner: Nobody in particular
Requestors: perl [...] csjewell.fastmail.us
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Fwd: Bug in version.pm's 0.76 Build.PL
Date: Fri, 24 Apr 2009 09:42:18 -0600
To: bug-version [...] rt.cpan.org
From: "Curtis Jewell" <perl [...] csjewell.fastmail.us>
It will not install (the distribution fails tests to the point of causing access errors in perl, and if the installation was forced, the use of it crashes perl with access errors) if you install it with the Build.PL and Module::Build 0.2808_01 (which is the version that comes with 5.10.0) on Win32. It WILL install and work when installed with the Makefile.PL. (I had this happening when generating distributions with Perl::Dist::WiX - since newer versions of Module::Build require newer versions of version.pm, version.pm needs installed first, so I can't update Module::Build before that point. I force building version.pm with the Makefile.PL in order to get around the problem, but it is one you should know about.) --Curtis -- Curtis Jewell swordsman@csjewell.fastmail.us %DCL-E-MEM-BAD, bad memory -VMS-F-PDGERS, pudding between the ears [I use PC-Alpine, which deliberately does not display colors and pictures in HTML mail]
Show quoted text
> - since newer versions of Module::Build require newer versions of > version.pm, version.pm needs installed first, so I can't update > Module::Build before that point. I force building version.pm with the > Makefile.PL in order to get around the problem, but it is one you > should > know about.)
I thought I had responded to this, but apparently not. Modern Module::Build bundles include a standalone version.pm module within them, so there should be no reason you cannot install Module::Build first. In addition, Perl 5.10.0 includes version.pm (0.74) itself as well, so installing version.pm 0.76 is only slightly worthwhile. Apart from that, you haven't given me much to work with and I don't have a Win32 box to test with. Can you attach transcripts of the build process with Build.pl and Makefile.pl, so I can compare and see if there is some difference. I suspect it has something to do with the the order of operations being different under Windows... Thanks for the report John
On Sun May 10 17:05:00 2009, JPEACOCK wrote: Show quoted text
> > - since newer versions of Module::Build require newer versions of > > version.pm, version.pm needs installed first, so I can't update > > Module::Build before that point. I force building version.pm with the > > Makefile.PL in order to get around the problem, but it is one you > > should > > know about.)
> > I thought I had responded to this, but apparently not. Modern > Module::Build bundles include a standalone version.pm module within > them, so there should be no reason you cannot install Module::Build > first. In addition, Perl 5.10.0 includes version.pm (0.74) itself as > well, so installing version.pm 0.76 is only slightly worthwhile. > > Apart from that, you haven't given me much to work with and I don't have > a Win32 box to test with. Can you attach transcripts of the build > process with Build.pl and Makefile.pl, so I can compare and see if there > is some difference. I suspect it has something to do with the the order > of operations being different under Windows... > > Thanks for the report > > John
I'll attach the Build.PL log now, and I'll get a Makefile.PL log to you soon (most likely tomorrow - I'll have figure out how to stop Strawberry building at the correct point. This is actually the log up until "Build test", because it's at that point that it fails.
Download debug.out
application/octet-stream 1.5k

Message body not shown because it is not plain text.

Download debug.err
application/octet-stream 5.5k

Message body not shown because it is not plain text.

On Thu Jun 11 18:32:21 2009, CSJEWELL wrote: Show quoted text
> I'll attach the Build.PL log now, and I'll get a Makefile.PL log to you > soon (most likely tomorrow - I'll have figure out how to stop Strawberry
Well, here are the bits that are useful: Generating script 'lib\version\version.lds' dlltool --def "lib\version\version.def" --output-exp "lib\version\version.exp" g++ -o "blib\arch\auto\version\vxs\vxs.dll" -Wl,--base-file,"lib\version\version.base" -Wl,--image-base,0x12140000 -mdll -s -L"C:\strawberry\perl\lib\CORE" -L"C:\strawberry\c\lib" "lib\version\version.lds" "lib\version\version.exp" dlltool --def "lib\version\version.def" --output-exp "lib\version\version.exp" --base-file "lib\version\version.base" g++ -o "blib\arch\auto\version\vxs\vxs.dll" -Wl,--image-base,0x12140000 -mdll -s -L"C:\strawberry\perl\lib\CORE" -L"C:\strawberry\c\lib" "lib\version\version.lds" "lib\version\version.exp" and lib\version\version.exp:fake:(.edata+0x38): undefined reference to `boot_version' lib\version\version.exp:fake:(.edata+0x3c): undefined reference to `boot_version' collect2: ld returned 1 exit status lib\version\version.exp:fake:(.edata+0x38): undefined reference to `boot_version' lib\version\version.exp:fake:(.edata+0x3c): undefined reference to `boot_version' collect2: ld returned 1 exit status It is trying to use the XS code and falling over; further test failures are caused by trying to use the pure Perl code instead. I'm not surprised that it would cause crashing. There may be more useful information a complete build log (not just the testing). I suspect it is something to do with the fact that Strawberry uses g++ for everything and whatever Module::Build is doing isn't working right. However, I don't know why the Makefile.PL code works (other than it being a more mature tool on Win32), so I think the solution would be: 1) install the pure Perl code instead (--perl_only to either the Build.PL or Makefile.PL); 2) stick with the Makefile.PL instead. Since this is really a Module::Build issue rather than a version.pm issue, I'm closing this ticket as WONTFIX. If I have time, I'll try to get Strawberry installed on a Win32 VM and try and research this some more, but there are a lot of more important things vying for attention at the moment... ;-) John