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):

• Scalar-List-Utils
• XML-Parser
• DBI
• DBD-mysql
• Bit-Vector

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.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.