This is the mail archive of the cygwin@sourceware.cygnus.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Cygwin, NT and Nutcracker


Jens Reimann <reim@pe-muc.de> 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 <reent.h> 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@sourceware.cygnus.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]