----- Original Message ----- From: "Steffen Mueller" <rt8363b02@sneakemail.com> To: <par@perl.org>; <danielmcbrearty@gmail.com>; <P.Schaffnit@access.rwth-aachen.de> Sent: Tuesday, October 31, 2006 10:07 PM Subject: Re: perl_ck_warn_d not found in perl58.dll (win 32) > Daniel McBrearty schrieb: > > maybe I'll mail activestate and ask them if there's a chance they > > could start making it available ... > > You'll probably have a hard time. They sell a competing product > (perlapp). It's not that they'd specifically remove PAR from their > automatic builds, I guess, but they won't go through a lot of trouble to > make it available. (Or at least I wouldn't if I was them.) I'm not so sure that they think that way :-) > > Anyhow, looking at the PAR test results on their build system, I see > that it's not PAR that can't be built, but one of its prerequisites > Getopt::ArgvFile. I wonder why, though, since Getopt::ArgvFile is a > simple pure-perl module if I've ever seen one. From http://ppm.activestate.com/BuildStatus/5.8-windows/windows-5.8/Getopt-ArgvFile-1.10.txt : D:\cpanrun\build\5-8-0\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib\lib', 'blib\arch')" t/*.t t/base.......# Failed test (t/resolvepathes.t at line 67) # Structures begin differing at: # $got->[7] = 'D:/cpanrudubious Test returned status 1 (wstat 256, 0x100) DIED. FAILED test 4 Failed 1/4 tests, 75.00% okay t/use1.............ok t/use2.............ok Failed Test Stat Wstat Total Fail Failed List of Failed ------------------------------------------------------------------------NMAK E : fatal error U1077: 'D:\cpanrun\build\5-8-0\bin\perl.exe' : return code '0xff' Stop. --- t\resolvepathes.t 1 256 4 1 25.00% 4 > Hence: If you "fix" Getopt::ArgvFile so that its tests pass on AS Perl > (they do on Strawberry win32), there'll probably a PAR from > ActiveState's repository. They may well do that, if asked. (Best to seek that sort of assistance from ActiveState's PPM mailing list.)>I would still suggest sticking to the > uwinnipeg or bribes builds, though. If the op has visual studio 6.0 (in which case he will be using the same compiler as was used to build his perl) I would probably be recommending that he build PAR himself. Otherwise, yes, I agree with you.Cheers,RobThread Previous