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: <19990817124239.6866.rocketmail@web114.yahoomail.com> Date: Tue, 17 Aug 1999 05:42:39 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Cygwin, NT and Nutcracker To: Jens Reimann Cc: cygwin AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Jens Reimann wrote: > the problem is (as described) that nutcracker(MSVC) und gcc both define the > iobs in a different way. So when I compile with gcc und link with gcc > Nutcracker can not find the MSVC iobs, when I compile with gcc und link > with the nutcracker libs, gcc does not find its iobs (which are defined for > each thread) > > So I just added a symbol FILE * _iob which fixes the linker warning (and > also _seems_ to work) but is that a real solution?? It sounds to me as if you're mixing C runtimes. It is possible to use gcc either cygwin or mingw32 to use the different runtime but it isn't going to be a simple matter of just compiling and linking. You'll have to ensure that the proper headers for the runtime you're using are being used. You may even have to supply the startup code. Beyond that you're into experimenting with the frontiers of compiler/runtime technology. === Earnie Boyd Newbies, please visit (If you respond to the list, then please don't cc me) _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com