RE: [rt.cpan.org #55660] [PATCH] Partial win64 support for Win32::API

[email protected] ("Stephen Bennett via RT")
Newsgroups perl.libwin32
Message-ID <[email protected]>
Mon Apr 26 18:01:24 2010: Request 55660 was acted upon.
Transaction: Correspondence added by [email protected]
       Queue: Win32-API
     Subject: RE: [rt.cpan.org #55660] [PATCH] Partial win64 support for Win32::API 
   Broken in: (no value)
    Severity: (no value)
       Owner: COSIMO
  Requestors: [email protected]
      Status: open
 Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=55660 >


Apologies for the delayed reply -- I was rather busy at the time and then subsequently just forgot about this.

> ###############################
> Test Summary Report
> -------------------
> t/00_API.t        (Wstat: 1280 Tests: 11 Failed: 0)
>   Non-zero exit status: 5
>   Parse errors: Bad plan.  You planned 25 tests but ran 11.
> t/01_Struct.t     (Wstat: 1280 Tests: 5 Failed: 0)
>   Non-zero exit status: 5
>   Parse errors: Bad plan.  You planned 7 tests but ran 5.
> Files=6, Tests=53, 19 wallclock secs ( 0.17 usr +  0.11 sys =  0.28 CPU)
> Result: FAIL
> Failed 2/6 test programs. 0/53 subtests failed.
> NMAKE : fatal error U1077: 'C:\_64\perl1007\bin\perl.exe' : return code
> '0xff'
> Stop.
> ###############################
>
> Is that as anticipated ?

No; the Win32::API tests should pass (and do on my build). Can you find out which tests exactly are failing? That looks somewhat like the testsuite is crashing perl; in which test?

> Now ... to try and find out why ml.exe is being called, instead of ml64.exe.

That sounds like your environment is set up for the 32-bit MSVC++ toolchain, instead of the x64 one. Assuming you're using the vcvars batch file to set up your environment for NMAKE, are you giving it the right arguments for an x64 build?

Accelrys Limited (http://accelrys.com)
Registered office: 334 Cambridge Science Park, Cambridge, CB4 0WN, UK
Registered in England: 2326316
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.