Hi,

I don't really know much about Configure scripts, but it looks to me that Configure tests for the compiler by running: 
$cc -o try $ccflags $ldflags try.c

[download]
If that fails, then Configure concludes that a C compiler is not available.

However, a failure could conceivably arise for other reasons - perhaps try.c is not a valid C file, or perhaps one (or more) of $cc, $ccflags and $ldflags has not been set appropriately and is screwing up the works.

What does try.c contain ? I think it ought to be: 
int main(int argc, char *argv[]) {
  return 0;
}

[download]
Can you successfully run 'cc -o try try.c' ? (I'm assuming that try.c did not cleaned up when Configure aborted.)

Cheers,
Rob

In reply to Re: abort while installing perl in Tru64 by syphilis
in thread abort while installing perl in Tru64 by xiaoyafeng

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.