public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Simon Gornall <simon@unique-id.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Newbie with socket problems...(pretty long)
Date: Mon, 09 Aug 1999 15:35:00 -0000	[thread overview]
Message-ID: <199908092235.RAA01600@mercury.xraylith.wisc.edu> (raw)
In-Reply-To: <37AF5469.67B8D34A@unique-id.com>

Simon Gornall <simon@unique-id.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@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: Mumit Khan <khan@xraylith.wisc.EDU>
To: Simon Gornall <simon@unique-id.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: Newbie with socket problems...(pretty long)
Date: Tue, 31 Aug 1999 23:49:00 -0000	[thread overview]
Message-ID: <199908092235.RAA01600@mercury.xraylith.wisc.edu> (raw)
Message-ID: <19990831234900.7SxEwJ48gYBjJrjLosE2lLgvdeoa9amkKN6h3GFyCdU@z> (raw)
In-Reply-To: <37AF5469.67B8D34A@unique-id.com>

Simon Gornall <simon@unique-id.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@sourceware.cygnus.com

  reply	other threads:[~1999-08-09 15:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-09 15:19 Simon Gornall
1999-08-09 15:35 ` Mumit Khan [this message]
1999-08-31 23:49   ` Mumit Khan
1999-08-31 23:49 ` Simon Gornall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=199908092235.RAA01600@mercury.xraylith.wisc.edu \
    --to=khan@xraylith.wisc.edu \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=simon@unique-id.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).