That won't work.
You have to use the compiler that perl was compiled with ( i have gcc in my path, but my perl was compiled with cl, which is also in my path).
All that stuff is stored in Config (use Config; aka `perl -V:.+');

A technique i've seen often is to get the compiler details out of %Config, and attempt to compile test.c, which is simply int main(){return 0}; Then attempt to run it. If you made it past those two, the user has a compiler, so the makefile gets written.

And of course, there is an override commandline option, which skips the check, and assumes there is a compiler installed.

The best technique by far , in my opinion, is not to worry or perform any checks. The users will figure out if s?he needs a compiler when they run make, you just make sure all your ducks are in order ;)(all the user has to do if they got a compiler is fill in a few path variables, and let it rip)

For examples of this see the makefiles for the following distributions (among others):

MJD says you can't just make shit up and expect the computer to know what you mean, retardo!
** The Third rule of perl club is a statement of fact: pod is sexy.

In reply to Re: Testing for compiler on Win32 by PodMaster
in thread Testing for compiler on Win32 by c

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.