Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id:	<199908092235.RAA01600@mercury.xraylith.wisc.edu>
To:	Simon Gornall <simon AT unique-id DOT com>
cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Newbie with socket problems...(pretty long)
In-Reply-To:	Your message of "Mon, 09 Aug 1999 23:21:30 BST."
	<37AF5469 DOT 67B8D34A AT unique-id DOT com>
Date:	Mon, 09 Aug 1999 17:35:23 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Note-from-DJ:	This may be spam

Simon Gornall <simon AT unique-id DOT com> writes:
> I've just downloaded a clean 'full install' of the B20.1 cygnus
> development
> environment, and I seem to be having problems with sockets. It's all
> linking
> correctly, and I can't seem to find anyone else with problems recently,
> so
> I assume I'm linking it incorrectly or something... If anyone cares to
> have a
> look and see what I'm doing wrong, I'd be very grateful. I'm *almost* at

I notice that you're using -mno-cygwin. You certainly want to read my
notes on using -no-cygwin available at:

  http://www.xraylith.wisc.edu/~khan/software/gnu-win32/

Also, while you're at the above URL, you may seriously consider upgrading
your compilers to gcc-2.95.

before doing things like:

> One thing I did have to do was move the libstdc++.a from the mwing32
> libraries directory to the 'standard'
> directory, or I got loads of 'undefined XXX' errors, where XXX where
> obviously global variables.

Remember that you're using Winsock, not Berkeley or POSIX sockets that's
common on Unix systems. For Winsock, you *have* to call WSAStartup
first (see windows docs on microsoft site or in your favorite w32 api
book). Unless you have other problems in the code, this should fix
it.

When you post asking for help, you really ought to try and explain 
better as to what problem you're having. For example, is it not 
connecting? Is it not opening the stream socket? This really saves
time when looking at others' code.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -