From: Mumit Khan <khan@NanoTech.Wisc.EDU>
To: Mark Schoenberg <mark@lpb.niams.nih.gov>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: sys/socket.h problemp
Date: Fri, 31 Dec 1999 13:28:00 -0000 [thread overview]
Message-ID: <Pine.HPP.3.96.991201182751.2256E-100000@hp2.xraylith.wisc.edu> (raw)
Message-ID: <19991231132800.3kBif_gtkbNkq8bDHaLAh-r6uWghlcR0c9F15LMh5TU@z> (raw)
In-Reply-To: <38444807.6EE67141@vinschen.de>
On Tue, 30 Nov 1999, Corinna Vinschen wrote:
> Mark Schoenberg wrote:
> >
> > What is wrong with my setup or the following 5-line program
> > [...]
> C:/CYGNUS/CYGWIN~1/H-I586~1/BIN/../lib/gcc-lib/i586-cygwin32/egcs-2.91.66/cc1.exe
> c:\windows\TEMP/cc1nGhch.i -quiet -dumpbase mtest.c -mno-cygwin -O2
> -version -o c:\windows\TEMP/ccvIlFqu.s
>
> You can't use cygwin sockets with -mno-cygwin. Try using winsock.h
> And don't change cygwin header files. It's not worth the incurring
> problems.
>
And while you're at it, please do read my mno-cygwin howto the points
out a few of these obvious gotcha's.
http://www.xraylith.wisc.edu/~khan/software/gnu-win32/#mno-cygwin
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-12-31 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-30 13:12 sys/socket.h problem Mark Schoenberg
1999-11-30 13:39 ` Cygnus - Admin
1999-11-30 23:39 ` Cygnus - Admin
1999-11-30 13:56 ` Corinna Vinschen
1999-11-30 23:39 ` Corinna Vinschen
1999-12-01 16:30 ` Mumit Khan [this message]
1999-12-31 13:28 ` sys/socket.h problemp Mumit Khan
1999-11-30 23:39 ` sys/socket.h problem Mark Schoenberg
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=Pine.HPP.3.96.991201182751.2256E-100000@hp2.xraylith.wisc.edu \
--to=khan@nanotech.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=mark@lpb.niams.nih.gov \
/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).