I use CCTYPE = MSVC90FREE
That would be version 15.something-or-other. I can actually use that, too - it doesn't seem to make much difference.
I don't get any -Wp64 deprecation warnings, so I've left that flag in. I guess it must still be relevant to my compiler. Ideally, the Makefile would be tweaked so that the flag is omitted for compilers such as yours.
Your suggested change of $(MINIPERL) to $(PERLEXE) does, of course, work fine for me. Maybe submit a perlbug report about this, along with your suggested fix.
Still no closer to understanding why your compiler builds a troublesome miniperl.
Cheers,
Rob | [reply]
[d/l]
[select] |
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] |