See Re^9: perl 5.14.0-RC1 is available for testing! and make a similar change for uudmap

or go ahead and add the path to those DLLs to your %PATH% (it should be $(CCHOME)\bin )

Example 

CCTYPE        *= GCC
.IF "$(CCTYPE)" == "GCC"
CCHOME        *= C:\MinGW
.ELSE
CCHOME        *= $(MSVCDIR)
.ENDIF

CCTYPE          *= GCC
.IF "$(CCTYPE)" == "GCC"
         GCC_VERSION *= $(shell gcc -dumpversion)
         GCC_MAJOR_VERSION *= $(GCC_VERSION:b:b)
         .IF  "$(GCC_MAJOR_VERSION)" == "4"
             CFLAGS          += -static-libgcc 
                LIBC          += -static-libgcc 
                GCC_4XX          *= define
         .ENDIF
.ENDIF



.IMPORT .IGNORE : PATH

.IF exist "$(CCTYPE)\bin"
    PATH    +:=;$(CCHOME)\bin;
.ELSE
    PATH    +:=;$(CCHOME);
.ENDIF

.EXPORT: PATH


__echo_GCC:
     @echo GCC_VERSION    $(GCC_VERSION)
     @echo GCC_MAJOR_VERSION    $(GCC_MAJOR_VERSION)
     @echo GCC_4XX  $(GCC_4XX)
     @echo CFLAGS  $(CFLAGS)
     @echo LIBC  $(LIBC)
     @echo 
     @echo 
     @echo RUN THIS MAKEFILE AS
     @echo           dmake && echo %path%
     @echo 
     @echo 
     @echo ###########
     @echo PATH
     @echo $(PATH)
     @echo ###########
     @echo PATH from SHELL (ie child process)
     @echo $(shell cmd /x /c echo %path%)
     @echo 
     @echo 
     $(NOOP)

[download]

output 

$ dmake
dmake: Executing shell macro: gcc -dumpversion
dmake: Executing shell macro: gcc -dumpversion
GCC_VERSION     4.7.0
dmake: Executing shell macro: gcc -dumpversion
GCC_MAJOR_VERSION       4
GCC_4XX  define
CFLAGS  -static-libgcc
LIBC  -static-libgcc


RUN THIS MAKEFILE AS
dmake && echo %path%


###########
PATH
C:\dmake-4.12-20090907-SHAY;C:\MinGW\bin; ;C:\MinGW\bin;
###########
PATH from SHELL (ie child process)
dmake: Executing shell macro: cmd /x /c echo %path%
C:\dmake-4.12-20090907-SHAY;C:\MinGW\bin; ;C:\MinGW\bin;

[download]

dmake sneaks in an extra trailing whitespace, must be a bug :/

In reply to Re: Problems building latest Perl build with Mingw64 by Anonymous Monk
in thread Problems building latest Perl build with Mingw64 by BAJA

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.