Hi, [EMAIL PROTECTED] wrote:
>Below is the error stack during 'make test': > > C:\Perl\bin\perl.exe "-MExtUtils::Command::MM" "-e" "test_harness(0, > 'inc', 'blib\lib', 'blib\arch')" t/01_constants.t t/02_gensym.t t/03_new_fh.t > t/04_fsopen_fh_arg.t t/05_sopen_fh_arg.t t/06_fsopen_access.t > t/07_sopen_access.t t/08_fsopen_share.t t/09_sopen_share.t > t/10_fsopen_fh_leak.t t/11_sopen_fh_leak.t t/12_variables.t t/13_pod.t >t/01_constants.........ok >t/02_gensym............ok >t/03_new_fh............ok >[...] >Failed 9/13 test scripts, 30.77% okay. 1195/1253 subtests failed, 4.63% okay. >NMAKE : fatal error U1077: 'C:\WINDOWS\system32\cmd.exe' : return code '0xff' >Stop. > > >Additional comments: >Several requests to send Windows error reports to Microsoft for perl.exe when >running tests > I had a similar error report from you before regarding another module of mine (Win32-UTCFileTime). The problem then was that you were using an ActivePerl, which is built using VC++ 6.0, but your own compiler was a later version (the free VC++ Toolkit, aka VC7, IIRC). I believe this is the same problem again. It is a known issue that you cannot pass CRT resources between different versions of the MS C runtime. VC6 uses the OS's msvcrt.dll, while VC7 uses its own msvc7XX.dll. So whenever CRT resources like filehandles are passed between the perl DLL (built by ActiveState to use msvcrt.dll) and these modules' DLLs (built by you to use msvc7XX.dll) you will get problems. I was able to workaround the issue in Win32-UTCFileTime because there was not much passing of affected resources between the various DLL's, but a similar workaround is not possible for Win32-SharedFileOpen. I did re-release both modules at the time with notes added to their INSTALL documents about this problem, e.g. see http://search.cpan.org/src/SHAY/Win32-SharedFileOpen-3.31/INSTALL. Thus, I would strongly recommend that you use the same compiler to build CPAN modules as was used to build Perl. If you don't have VC6 available, then you could consider building your own Perl using whatever compiler you have got. There are some notes in the README.win32 (ala perlwin32 manpage) about building Perl on Win32, including a section specifically about how to build it with the free VC++ Toolkit, if that's what you are using. Search for the section entitled "Microsoft Visual C++ Toolkit 2003" in http://search.cpan.org/dist/perl/README.win32. - Steve ------------------------------------------------ Radan Computational Ltd. We would like to take this opportunity to wish all our customers, suppliers and colleagues seasons greetings. We will not be sending corporate greetings cards this year. Instead, we will be making a donation to charity. 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.
