public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "THORMODSEN, ARNE D (HP-Corvallis, ex1)" <arnet@ex.cv.hp.com>
To: cygwin@sourceware.cygnus.com
Subject: new user question - Cygwin and Mingw32 compatibility?
Date: Tue, 09 Mar 1999 13:40:00 -0000	[thread overview]
Message-ID: <EBC089F12684D211AF5600A0C9DEFB771DD4BE@cvex04.cv.hp.com> (raw)

This is a more compact version of a question I sent out awhile back.

It there some basic incompatibility between using windows sockets via the cygwin
includes and console IO via mingw32?

The small example program below will compile with gcc, linking with wsock32 and
msvcrt, but core dumps with a STATUS_STACK_OVERFLOW when the dlls are loading,
before it even runs.  I've found several hints as to what might be the problem
in the mail archives, but nothing specific to this.  A cygcheck on the binary
shows both msvcrt.dll and wsock32.dll, which makes sense.  But by trial and
error I've found that these guys seem to collide if both are loaded.  Is this
simply a basic incompatibility, or what?

Thanks much,

--arne

Arne Thormodsen



// donoth.c
//
// Simplest case for error
// Does nothing

#define Win32_Winsock

#include <stdio.h>
#include <stdlib.h>
#include <windows.h>
#include <mingw32/conio.h>


main(argc,argv)
int argc;
char *argv[];
{
  WSADATA *data;
  int i,j;

  data=malloc(sizeof(WSADATA));
  i = WSAStartup(MAKEWORD(1,1),data);

  j=_kbhit();
  
  WSACleanup();
  free(data);

}

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

WARNING: multiple messages have this Message-ID
From: "THORMODSEN, ARNE D (HP-Corvallis, ex1)" <arnet@ex.cv.hp.com>
To: cygwin@sourceware.cygnus.com
Subject: new user question - Cygwin and Mingw32 compatibility?
Date: Wed, 31 Mar 1999 19:45:00 -0000	[thread overview]
Message-ID: <EBC089F12684D211AF5600A0C9DEFB771DD4BE@cvex04.cv.hp.com> (raw)
Message-ID: <19990331194500.lU4gDQMbuL6ublX6BzDune7npCyP3-RP8KMKeyMwWPU@z> (raw)

This is a more compact version of a question I sent out awhile back.

It there some basic incompatibility between using windows sockets via the cygwin
includes and console IO via mingw32?

The small example program below will compile with gcc, linking with wsock32 and
msvcrt, but core dumps with a STATUS_STACK_OVERFLOW when the dlls are loading,
before it even runs.  I've found several hints as to what might be the problem
in the mail archives, but nothing specific to this.  A cygcheck on the binary
shows both msvcrt.dll and wsock32.dll, which makes sense.  But by trial and
error I've found that these guys seem to collide if both are loaded.  Is this
simply a basic incompatibility, or what?

Thanks much,

--arne

Arne Thormodsen



// donoth.c
//
// Simplest case for error
// Does nothing

#define Win32_Winsock

#include <stdio.h>
#include <stdlib.h>
#include <windows.h>
#include <mingw32/conio.h>


main(argc,argv)
int argc;
char *argv[];
{
  WSADATA *data;
  int i,j;

  data=malloc(sizeof(WSADATA));
  i = WSAStartup(MAKEWORD(1,1),data);

  j=_kbhit();
  
  WSACleanup();
  free(data);

}

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com


             reply	other threads:[~1999-03-09 13:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-09 13:40 THORMODSEN, ARNE D (HP-Corvallis, ex1) [this message]
1999-03-31 19:45 ` THORMODSEN, ARNE D (HP-Corvallis, ex1)

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=EBC089F12684D211AF5600A0C9DEFB771DD4BE@cvex04.cv.hp.com \
    --to=arnet@ex.cv.hp.com \
    --cc=cygwin@sourceware.cygnus.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).