Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com List-Unsubscribe: List-Archive: List-Help: , Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199908012151.QAA04263@mercury.xraylith.wisc.edu> To: marcel DOT cox AT ibm DOT net cc: Cygwin Subject: Re: GCC 2.95-Mingw32: winsock.h is not C++ enabled In-Reply-To: Your message of "Sun, 01 Aug 1999 20:22:10 +0200." Date: Sun, 01 Aug 1999 16:51:09 -0500 From: Mumit Khan Marcel Cox writes: > The winsock.h file from the mingw32 version of GCC 2.95 is not C++ > enabled. You get link time errors because the names for the winsock > functions are mangled. The solution is to include the usual C11 enabling > stuff in the header file, e.g. > > near the beginning of the file: > > #ifdef __cplusplus > extern "C" { > #endif /* __cplusplus */ > > near the end: > > #ifdef __cplusplus > } > #endif /* __cplusplus */ Thanks. I used Anders' last snapshot (+ a few local changes), and it's indeed missing the C linkage spec needed for C++ code. It looks it's fixed in Cygwin winsup snapshots, and in retrospect, I should've spent some time merging those changes in. I'm assuming Anders will put out a new release in due time, and that will fix these little problems. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com