This is funny (or not actually :( ) Now when I try to compile Socket I get the same error. 
-bash-3.00$ make test
PERL_DL_NONLAZY=1 /usr/bin/perl "-MExtUtils::Command::MM" "-e" "test_h
+arness(0, 'blib/lib', 'blib/arch')" t/*.t
t/Socket.t ...... Can't load '/home/JD02911/Socket/blib/arch/auto/Sock
+et/Socket.so' for module Socket: ld.so.1: perl5.12.0: fatal: relocati
+on error: file /home/JD02911/Socket/blib/arch/auto/Socket/Socket.so: 
+symbol inet_aton: referenced symbol not found at /usr/local/lib/perl5
+/5.12.0/sun4-solaris/DynaLoader.pm line 200.

[download]
Only the paths are different, I placed the Socket folder containing all the files and the folder t with all of its files , in my home directory. Should I place it somewhere else? (In /usr/local/perl perhaps? )

In reply to Re^8: Can't build modules that load Socket.so by MikeMokkas
in thread Can't build modules that load Socket.so by MikeMokkas

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.