Thanks almut, cdarke for the /E tip. It revealed that there's a function called 'gpsi' in the pari source, and I guess that was the root of the problem the compiler was having with the 'gpsi' identifier. I couldn't find out (didn't look too hard) what was changing the name of the identifier from 'lpsi' to 'gpsi' - in the end I just changed the 2 occurrences of 'lpsi' in WinUser.h to 'lxpsi' and that got me passed that hurdle.

Next problem was: 
kernel1.c(223) : error C4235: nonstandard extension used : '__asm' key
+word not supported on this architecture

[download]
Is that telling me that inlining of assembly code is not supported on this architecture ? Or does it just mean that one needs to use a different keyword and/or technique to inline assembly code ?

Finally, I tried a straight C build (no asm). That compiled ok, but resulted in a number of segfaults and test failures during the running of the test suite.

I think I'll just settle for the 32-bit build - ftm, anyway.

Cheers,
Rob
Update:"ftm" eq "for the moment". (I think there are some who might have thought it meant something else :-)

In reply to Re^2: [OT] Building Math::Pari on M$ Windows by syphilis
in thread [OT] Building Math::Pari on M$ Windows by syphilis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.