This is the mail archive of the cygwin@sourceware.cygnus.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Question about -mno-cygwin.
- To: "Arcadio A. Sincero Jr." <asincero@sinceronet.ddns.org>
- Subject: Re: Question about -mno-cygwin.
- From: Mumit Khan <khan@xraylith.wisc.edu>
- Date: Tue, 9 Feb 1999 01:13:21 -0600 (CST)
- cc: Gnu-Win32 Mailing List <gnu-win32@cygnus.com>
- Delivered-To: listarch-cygwin@sourceware.cygnus.com
- Delivered-To: mailing list cygwin@sourceware.cygnus.com
- In-Reply-To: <Pine.LNX.4.05.9902082047160.6574-100000@intranet.sincero.net>
- Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
- Sender: cygwin-owner@sourceware.cygnus.com
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@sourceware.cygnus.com