Strawberry's gcc-generated libs won't talk to Sybase's client libs, so I am back to compiling using VC2012, full edition.

-perl 5.18.1

-I'm on a Win7 machine, 64 bit.

-I'm using a 64 bit compiler:

U:\perlbuild\tools>cl
Microsoft (R) C/C++ Optimizing Compiler Version 17.00.50727.1 for x64
Copyright (C) Microsoft Corporation.  All rights reserved.

usage: cl [ option... ] filename... [ /link linkoption... ]

U:\perlbuild\tools>

[download]

I have read the README.win32 and set the appropriate values in the win32\Makefile file. But when I compile, I get lots of size mismatch warnings. Here is the unique set:

conversion from 'IV' to 'DWORD', possible loss of data
conversion from 'IV' to 'I32', possible loss of data
conversion from 'IV' to 'U32', possible loss of data
conversion from 'IV' to 'const I32', possible loss of data
conversion from 'IV' to 'const U32', possible loss of data
conversion from 'IV' to 'const int', possible loss of data
conversion from 'IV' to 'int', possible loss of data
conversion from 'IV' to 'volatile U32', possible loss of data
conversion from 'PADOFFSET' to 'I32', possible loss of data
conversion from 'PADOFFSET' to 'U32', possible loss of data
conversion from 'SOCKET' to 'int', possible loss of data
conversion from 'STRLEN' to 'NV', possible loss of data
conversion from 'UINT_PTR' to 'UINT', possible loss of data
conversion from 'UV' to 'I32', possible loss of data
conversion from 'UV' to 'NV', possible loss of data
conversion from 'UV' to 'U32', possible loss of data
conversion from 'UV' to 'const unsigned int', possible loss of data
conversion from 'UV' to 'gid_t', possible loss of data
conversion from 'UV' to 'int', possible loss of data
conversion from 'UV' to 'unsigned int', possible loss of data
conversion from '__int64' to 'I32', possible loss of data
conversion from '__int64' to 'U16', possible loss of data
conversion from '__int64' to 'U32', possible loss of data
conversion from '__int64' to 'const I32', possible loss of data
conversion from '__int64' to 'const U32', possible loss of data
conversion from '__int64' to 'const int', possible loss of data
conversion from '__int64' to 'const long', possible loss of data
conversion from '__int64' to 'int', possible loss of data
conversion from '__int64' to 'long', possible loss of data
conversion from '__int64' to 'unsigned int', possible loss of data
conversion from '__int64' to 'volatile I32', possible loss of data
conversion from 'const IV' to 'I32', possible loss of data
conversion from 'const IV' to 'int', possible loss of data
conversion from 'const IV' to 'uid_t', possible loss of data
conversion from 'const PADOFFSET' to 'I32', possible loss of data
conversion from 'const UV' to 'I32', possible loss of data
conversion from 'const UV' to 'U32', possible loss of data
conversion from 'const UV' to 'gid_t', possible loss of data
conversion from 'const UV' to 'uid_t', possible loss of data
conversion from 'const __int64' to 'I32', possible loss of data
conversion from 'fpos_t' to 'long', possible loss of data
conversion from 'intptr_t' to 'int', possible loss of data
conversion from 'size_t' to 'DWORD', possible loss of data
conversion from 'size_t' to 'I32', possible loss of data
conversion from 'size_t' to 'U32', possible loss of data
conversion from 'size_t' to 'U8', possible loss of data
conversion from 'size_t' to 'const I32', possible loss of data
conversion from 'size_t' to 'const int', possible loss of data
conversion from 'size_t' to 'int', possible loss of data
conversion from 'size_t' to 'long', possible loss of data
conversion from 'size_t' to 'unsigned int', possible loss of data
conversion from 'size_t' to 'unsigned long', possible loss of data

[download]

I'm thinking I'm missing a flag setting somewhere. Here is a sample compile command:

    cl -c -nologo -GF -W3 -I..\lib\CORE -I.\include -I. -I.. -DWIN32 -
+D_CONSOLE -DNO_STRICT -DWIN64 -DCONSERVATIVE -D_CRT_SECURE_NO_DEPRECA
+TE -D_CRT_NONSTDC_NO_DEPRECATE -DPERLDLL -DPERL_CORE   -O1 -MD -Zi -D
+NDEBUG -GL -fp:precise -DPERL_IS_MINIPERL -Fo.\mini\win32thread.obj w
+in32thread.c

[download]

I'll keep testing, but if someone has done this and would like to point out if I am missing a flag somewhere, I'd appreciate it.

Thanks

In reply to Warnings building Perl itself on Windows 64 by mpersico

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.