Your documentation link went to the original parent node. A little searching shows this: http://gcc.gnu.org/onlinedocs/gcc-4.3.0/gcc/Link-Options.html#Link-Options being what you're citing.

I see what you're saying, but notice this option:

-static On systems that support dynamic linking, this prevents linking with the shared libraries. On other systems, this option has no effect.

Personal experience with GCC (including and especially on Solaris) indicates that if you have libname.so and libname.a, then the .so is preferred when building.

If you only linked against libname.a, then you wouldn't need the -static command line flag.

In reply to Re^6: Error during compilation of 5.8.8 on solaris 10 by Sinistral
in thread Error during compilation of 5.8.8 on solaris 10 by mmakarczyk

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.