in reply to Re^5: Can't build modules that load Socket.so
in thread Can't build modules that load Socket.so

I found a similar problem report in perl's bug reports about Socket on Solaris: http://rt.perl.org/rt3/Public/Bug/Display.html?id=2930 , do you know how to add -lresolv to appear in LIBS together with the other libraries? (Is there any way of doing that without recompiling whole perl?).
  • Comment on Re^6: Can't build modules that load Socket.so

Replies are listed 'Best First'.
Re^7: Can't build modules that load Socket.so
by Anonymous Monk on Sep 22, 2010 at 10:07 UTC
[reply]
[d/l]
      This is funny (or not actually :( ) Now when I try to compile Socket I get the same error.
      Read more... (1025 Bytes)
      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? )
[reply]
[d/l]
        This is funny (or not actually :( ) Now when I try to compile Socket I get the same error.

        From what I've seen, it seems like typical solaris experience :(

        It also seems like your admin should have caught/resolved this when installing perl

        Trying search again: Socket.so fatal relocation error inet_aton→ Re: [perl #17535] inet_aton not found during test phase - nntp.perl.org 

        =item __inet_* errors

If you receive unresolved symbol errors during Perl build and/or test
referring to __inet_* symbols, check to see whether BIND 8.1 is
installed.  It installs a /usr/local/include/arpa/inet.h that refers t
+o
these symbols.  Versions of BIND later than 8.1 do not install inet.h
in that location and avoid the errors.  You should probably update to 
+a
newer version of BIND (and remove the files the old one left behind).
If you can't, you can either link with the updated resolver library pr
+ovided
with BIND 8.1 or rename /usr/local/bin/arpa/inet.h during the Perl bui
+ld and
test process to avoid the problem.

        [download]
        So give that a try :D

        Should I place it somewhere else? (In /usr/local/perl perhaps? )

        No

[reply]
[d/l]

In Section Seekers of Perl Wisdom