If you remember, I long ago aquired a copy of bufferoverflowU.lib and stuck it in my compiler lib directory. It satisfies the linker's need to find it, even though it is never called upon to supply any entrypoints.

But I guess that the bufferoverflowU problem could be avoided by: 

# The 64 bit Platform SDK compilers contain a runtime library that doe
+sn't
# include the buffer overrun verification code used by the /GS switch.
# Since the code links against libraries that are compiled with /GS, t
+his
# "security cookie verification" must be included via bufferoverlow.li
+b.
!IF "$(WIN64)" == "define" && ( "$(CCTYPE)" == "MSVC80" || "$(CCTYPE)"
+ == "MSVC80FREE" )
LIBBASEFILES    = $(LIBBASEFILES) bufferoverflowU.lib
!ENDIF

[download]

That said, it is intriguing that you are not having the same problem with exetype.pl. It is only a problem here when run under miniperl.exe... It was at this point it dawned on my that in order to be modifying wperl.exe, it had just copied a successfully built perl.exe.

So, insteand of using $(MINIPERL) it should be possible to use $(PERLEXE) to work around the problem with miniperl. And it is and does. With that change, nmake install completes successfully. 

$(PERLEXE): $(PERLDLL) $(CONFIGPM) $(PERLEXE_OBJ) $(PERLEXE_RES)
    $(LINK32) -subsystem:console -out:$@ -stack:0x1000000 $(LINK_FLAGS
+) \
        $(LIBFILES) $(PERLEXE_OBJ) $(SETARGV_OBJ) $(PERLIMPLIB) $(PERL
+EXE_RES)
    $(EMBED_EXE_MANI)
    copy $(PERLEXE) $(WPERLEXE)
#    $(MINIPERL) -I..\lib bin\exetype.pl $(WPERLEXE) WINDOWS
    $(PERLEXE) -I..\lib bin\exetype.pl $(WPERLEXE) WINDOWS

[download]

And while we're at it, the spurious -Wp64 is deprecated and will be remove warning could go: 

!IF "$(WIN64)" == "define"
DEFINES        = $(DEFINES) -DWIN64 -DCONSERVATIVE
!IF "$(CCTYPE)" == "MSVC80" || "$(CCTYPE)" == "MSVC80FREE" 
OPTIMIZE    = $(OPTIMIZE) -Wp64 -fp:precise
!ELSE
OPTIMIZE    = $(OPTIMIZE) -fp:precise
!ENDIF
!ENDIF

[download]

Would those changes work on your 2003 setup?

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.
RIP an inspiration; A true Folk's Guy

In reply to Re^3: Perl 5.12.0 has been released! (exetype problem 64-bit) by BrowserUk
in thread Perl 5.12.0 has been released! by ikegami

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.