Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199908170658.BAA10887@mercury.xraylith.wisc.edu> To: Jens Reimann cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: Cygwin, NT and Nutcracker In-Reply-To: Your message of "Tue, 17 Aug 1999 08:41:45 +0200." <37B90429 DOT 92002296 AT pe-muc DOT de> Date: Tue, 17 Aug 1999 01:58:15 -0500 From: Mumit Khan Jens Reimann writes: > > currently I'm working in a project where I have to port Unix source to > NT. The problem is that I don't want to use MS VC as compiler! Now i > started compiling my applications using Cygwin and Nutcracker. There > were some problems (syntax, defines, etc) but now I'm through and have > my applications running. You have to explain your setup a bit more. What part of Nutcracker are you using? If it's runtime, Nutcraker is not known to be compatible with Cygwin, so the issue becomes moot. Unlike the Unix or VMS world, the various windows32 runtimes are simply not compatible, and you can't mix and match. You can't do that with even MS's own incompatible runtimes -- crtdll and msvcrt -- let alone "foreign" ones such as Cygwin, UWIN, etc. > The last problem which had to be fixes was, that Nutcracker defined to > stdio streams as follows: > > extern FILE *_iob; > > #define stdin (&_iob[0]) > #define stdout (&_iob[1]) > #define stderr (&_iob[2]) > > where gnu defines them in the include with one for each > thread. This is all correct for Cygwin, and so unless you can provide a testcase (not for Nutcracker please, but for Cygwin), it'll be hard to figure out what is wrong. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com