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

[email protected] ("[email protected] via RT")
Newsgroups perl.libwin32
Message-ID <[email protected]>
Fri Apr 02 01:44:09 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 >



----- Original Message ----- 
From: "Sisyphus" <[email protected]>

>
> I'll try and get hold of a suitable ml.exe.
>

Duh - I already have one. But it's called ml64.exe, not ml.exe.
Anyway, renaming ml64.exe to ml.exe (temporarily) allows the build to 
complete.

For me, There are some failing tests (including a couple of segfaults):

###############################
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 ?

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

Cheers,
Rob
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.