Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com
Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
X-Authentication-Warning: modi.xraylith.wisc.edu: khan owned process doing -bs
Date: Tue, 9 Feb 1999 01:13:21 -0600 (CST)
From: Mumit Khan <khan AT xraylith DOT wisc DOT edu>
To: "Arcadio A. Sincero Jr." <asincero AT sinceronet DOT ddns DOT org>
cc: Gnu-Win32 Mailing List <gnu-win32 AT cygnus DOT com>
Subject: Re: Question about -mno-cygwin.
In-Reply-To: <Pine.LNX.4.05.9902082047160.6574-100000@intranet.sincero.net>
Message-ID: <Pine.SUN.3.93.990209011131.12079E-100000@modi.xraylith.wisc.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Mon, 8 Feb 1999, Arcadio A. Sincero Jr. wrote:

> Hello Gnu-Win32 Mailing List,
> 	
> 	I have a question concerning the -mno-cygwin command line switch.
> Will objects compiled without the -mno-cygwin switch link fine with
> objects compiled with it?  I ask because I noticed that if you want to
> build binaries using the -mno-cygwin switch, you need to link against
> Mingw32-specific versions of libstdc++ (and I assume Mingw32-specific
> versions of libobjc and libg2c as well, but I don't know for sure since I
> don't use Objective C or Fortran).

Yes, you need the migwn32 target libraries if you're linking against
libm.a, libstdc++ (C++), libiberty (BSD'ish porting routines), what not. 
I have these libraries on my site:

  ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/cygwin/egcs-1.1.1/

Of course, this is assuming you've upgrade to egcs-1.1.1.

Regards,
Mumit


--   
Want to unsubscribe from this list?                             
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com