AHA, typical dumb makefile and I forgot to grep :)

That makefile is really really unreadable (someone should indent it, rewrite it)

I shouldn't need to know anything about this :) The GCC_4XX way should be automatic one way or another, something like 

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

[download]
Or my way (untested) 
.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 
    .ENDIF
.ENDIF

[download]
Checking my make commands, a test makefile.mk 
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

__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)
    $(NOOP)

[download]
how it runs (output) 
$ dmake -f makefile.mk
dmake: Executing shell macro: gcc -dumpversion
dmake: Executing shell macro: gcc -dumpversion
GCC_VERSION   4.5.2
dmake: Executing shell macro: gcc -dumpversion
GCC_MAJOR_VERSION   4
GCC_4XX  define
CFLAGS  -static-libgcc
LIBC  -static-libgcc

[download]

Not sure how that fits in with your method of building. I've only ever built perl with gcc by running dmake -f makefile.mk

Yup, thats what I do, the -f makefile.mk isn't mandatory since that is the default

In reply to Re^3: perl 5.14.0-RC1 is available for testing! by Anonymous Monk
in thread perl 5.14.0-RC1 is available for testing! by Tux

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.