From: ts <decoux@...>
Date: 2002-10-25T01:40:43+09:00
Subject: Re: require socket - standalone file ?

>>>>> "G" == Groenenberg, Ron <rgroenenberg@atsautomation.com> writes:

G> Does such a statement imply that a file 'socket.rb' must exist ?

 No,
 
G> ./ext/extinit.c also seems to need addition of 'rb_provide( socket.so );'
G> but we cannot do dynamic loading.  Are we __ out of luck ?

 If you compile statically ruby and ruby *can build* the module socket it
 will add automatically the lines

        Init_socket();
        rb_provide("socket.so");


 in ext/extinit.c

 This is these lines which make the line 'require "socket"' work even if
 you  don't have dynamic loading (i.e. in this case ruby will not use
 dynamic loading for the module socket).

 Apparently, in your case, ruby *can't* build the module socket, because it
 give the message
 
G> checking for socket()... no
   ^^^^^^^^^^^^^^^^^^^^^^^^^^^

 At this step the module socket was not build and not statically linked
 with ruby, this is why socket is not available

 To make it work, ruby must be able to compile this extension.


Guy Decoux