From:	"John S. Fine" <johnfine AT erols DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: RSXNTDJ WINSOCK C++ ???
Date:	Wed, 03 Nov 1999 12:59:10 -0500
Lines:	25
Message-ID:	<382077EE.5A53@erols.com>
References:	<381F7D9B DOT 541B AT erols DOT com> <NQNT3.72$9L DOT 6460 AT nnrp1 DOT ptd DOT net>
Mime-Version:	1.0
X-Trace:	gNgK5Q3fD0/mOyt5dsRZ1zxUNopNjLBG6iAqfvf7fWg=
X-Complaints-To:	abuse AT rcn DOT com
NNTP-Posting-Date:	3 Nov 1999 18:01:48 GMT
X-Mailer:	Mozilla 3.01 (Win95; U)
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

John Bauman wrote:
> 
> Uhh, idea, put  an
> extern "C" {
> ...
> }
> (I think that's what it is) block around all the declares in the header.
> John S. Fine wrote in message <381F7D9B DOT 541B AT erols DOT com>...
. . .
> >  All the WINSOCK symbols come up undefined.  I used OBJDUMP
> >to find out why and discovered that in the libwsock32.a that
> >I found and the one I built using makelib, all the names
> >are unmangled "C" names.  In all my .o files, all those
> >names are mangled C++ names.

  I had already tried putting extern "C" { around the #include
of winsock.h.  That had no effect.  I haven't a clue why not.

  Now I've tried putting extern "C" inside winsock.h in front
of every declaration for an entry point my program uses.  That
gets rid of the link time errors, but when I run the program,
none of the WINSOCK functions work.
-- 
http://www.erols.com/johnfine/
http://www.geocities.com/SiliconValley/Peaks/8600/

- Raw text -