----- Original Message ----- From: "Bastad David" <[EMAIL PROTECTED]> To: "Tomas Doran" <[EMAIL PROTECTED]> Cc: "Schupp Roderich (extern) BenQ MD PD SWP 2 CM MCH" <[EMAIL PROTECTED]>; <[email protected]> Sent: Monday, October 31, 2005 5:16 PM Subject: Re: PAR bug?
> Thanks for your help!!! > > I installed PAR-587 but still have the "perl58dll" error message. Also,I still have the following error when I run my executable " Can't locate object method "new" via package "XML::SAX::PurePerl" at XML/SAX/ParserFactory.pm line 43. > > I attached my script as well as the XML file I'm trying to extract the information from.... I'm just curious, can you package the script and run it on your system (run the executable with .xml fle in the same folder).. If the executable works, what is your config? > > Kind of stuck with this issue .. > Works fine for me (perl 5.8.7, Windows 2000, PAR-0.89) - both as a perl script and as a PAR built executable. (If I transfer the executable and the xml file to another machine that doesn't have perl, it still works fine.) What version of perl was being run when the PAR executable was built ? What version of PAR are you using to build the executable ? As I understand it, there are 2 ways to avoid the PL_memory_wrap error: 1) Build the executable using perl 5.8.7. (It then won't matter which version of perl was used to build your PAR, so long as it was in the range 5.8.0-5.8.7.) 2) Use a PAR that was built using a version of perl that is in the range 5.8.0-5.8.6. (It then won't matter which version of perl you ran when building the executable, so long as it was in the range 5.8.0-5.8.7.) David Bastad claims to be running perl 5.8.7, and yet also claims to be getting the PL_memory_wrap error. That makes absolutely no sense to me, because the "procedure entry point PL_memory_wrap" can definitely be located in a 5.8.7 version of the perl58.dll. My understanding might be deficient - though it's not entirely clear to me that David is *necessarily* contradicting my understanding. Perhaps he's running perl 5.8.7, but his executable was built on perl 5.8.6 (or earlier) using a PAR that was compiled on perl 5.8.7. I think that would still produce the PL_memory_wrap error whenever the executable was run. Cheers, Rob
