At 5:01 PM +0530 9/29/06, Prabhu, Anantha (STSD) wrote: >Hi, > >I did check for configure.log but couldn't find one after running @ >configure -"de". Following is the output of >$ sea config.h socket > * to get socket ioctl options, like SIOCATMARK. > * include <sys/un.h> to get UNIX domain socket definitions. >/* HAS_SOCKET: > * This symbol, if defined, indicates that the BSD socket interface >is >/* HAS_SOCKETPAIR: > * This symbol, if defined, indicates that the BSD socketpair() >call is >#undef HAS_SOCKET /**/ >#undef HAS_SOCKETPAIR /**/ > * available to send structured socket messages. > * available to send structured socket messages. > * available to test whether a socket is at the out-of-band mark. > * various socket calls (just the base type, not the pointer-to). >$ > >I don't know why the above things come in my config.h? Any >suggestions/advice is highly appreciated.
Something's quite off about your configuration. What source archive did you start with and what is the exact command you used to unpack it? What is the full output of your configuration session? I would recommend wiping the build directory and starting over at this point, and starting over with 5.8.8 rather than 5.8.6 as long as you are building from scratch. >I would also like to know, how can I build the perl without socket >support? Answer "NONE" to the configuration question about which socket stack you want to use. I don't guarantee that will still work as it hasn't been tested in a long time. It's a holdover from the days when it was more common to have VMS systems without TCP/IP stacks. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
