Indeed, there were two exactly same places with that incompatibilities between Borland C++ and MSVC++ compilers, and I forgot to mention them earlier. In order to compile, I edited that file in error (zconf.h) in two places just to throw away a couple of lines for Borland compiler some version, so I stepped forward, and that was like a right direction.
Seems to me like "MakeMaker" is to blame here. Although I saw following places:
#if (defined(__BORLANDC__)&&(__BORLANDC__<=0x520)) \
|| (defined(__MINGW32__) && !defined(_ANONYMOUS_UNION))
.......
#endif
in perl source code distribution, which are essentially same as we faced.
BTW do you wish for me to email my build directory for reference? It's ~1Mb in size.
addition: may be we should prepare compatibility patch for miscellaneous compilers on win32 systems and sent it to author of a module?
Courage, the Cowardly Dog
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.