That would be version 15.something-or-other.
Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 15.00.30729.01 for 80x86
Ideally, the Makefile would be tweaked so that the flag is omitted for compilers such as yours.
The mod I posted already did that.
Still no closer to understanding why your compiler builds a troublesome miniperl..
I'm not sure if you saw it, but I got this far. But once I realised that I had the newly built full perl executable available for modifying wperl.exe, and that worked, I didn't look any further for the miniperl.exe problem.
I'll try and work up a Makefile patch later.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply]
[d/l]
[select] |
The mod I posted already did that
So it did .... not paying proper attention, again.
I'm not sure if you saw it, but I got this far.
Yes, I saw that, and I guess it constitutes some sort of understanding. Like you, I don't see any *need* to investigate the miniperl trouble any further (assuming your patch is acceptable to the powers that be). Still ... it's strange that this problem arose.
Cheers,
Rob
| [reply] |
Still ... it's strange that this problem arose.
I suspect the heart of it lies behind one of the bazillion of the following warning that are produced by the build.
The optimist in me once hoped that it would require a few typedef changes in the header files, but these warnings are so pervasive that a patch to fix them up would probably affect 10% of the lines in the entire codebase--extensions and all :(
-
-
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
| [reply]
[d/l] |