INST_ARCH    = \$(ARCHNAME)

That change alone seems to fix the problem for me.
Alternatively, I can leave the GNUmakefile in it's original state and pass INST_ARCH=\MSWin32-x64-multi-thread as one of the arguments passed to 'make'.
Both result in a perl whose @INC is: 
 INST_TOP/site/lib/MSWin32-x64-multi-thread
 INST_TOP/site/lib
 INST_TOP/lib/MSWin32-x64-multi-thread
 INST_TOP/lib

[download]
Also existent is: 
 INST_TOP/bin
 INST_TOP/bin/MSWin32-x64-multi-thread

[download]
I'm not entirely sure what an archnamed build should look like - but the build I've got feels right and looks sane.
I haven't tried specifying an INST_ARCH value that doesn't match $Config{archname}. (Not sure what to expect with that.)

I think I might even start building my perls this way.

Normally, for every version of perl that I build, I have 4 different configurations (ie 4 different archnames).
Building them with INST_ARCH into the same INST_TOP would make good sense and reduce duplication.

Thanks for chiming in jcb.
It's a pity you didn't get in there a bit earlier. (Would have saved me some time, effort and embarrassment ;-)

Cheers,
Rob

In reply to Re^2: Perl compilation on Windows with INST_ARCH set fails by syphilis
in thread Perl compilation on Windows with INST_ARCH set fails by ivpri

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.