It was a bad idea to rely on _G_HAVE_SYS_SOCKET. In version 5.0 I just assume that sockets are available if __unix__ is defined.
On Wed, Oct 09, 2002 at 11:36:27PM -0500, Michael Davis wrote: > Hey guys, > > I am compiling Crypto++ 4.2 on Red Hat Linux 7.3. This machine is 100% > stock. When I compiled Crypto++ 4.2 I noticed sockets were not available > (reported from cryptest.exe) because _G_HAVE_SYS_SOCKET is NOT defined in > /usr/include/_G_config.h even though Linux DOES has a sys/socket.h AND is > compatible with Berkley sockets. > > I am using gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110) on Linux > syn 2.4.18-3 #1 Thu Apr 18 07:37:53 EDT 2002 i686 unknown > > Anyone have an answer? If I put #define _G_HAVE_SYS_SOCKET 1 in > /usr/include/_G_config.h and recompile Crypto++ sockets work perfectly. > > Michael Davis >
