Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Wed, 16 Jun 1999 11:58:52 -0700 From: Geoffrey Noer To: Mumit Khan Cc: cygwin@sourceware.cygnus.com Subject: Re: odd 'configure' problems Message-ID: <19990616115852.A17505@cygnus.com> References: <199906152225.SAA05428@jaj.com> <199906152139.QAA11604@mercury.xraylith.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199906152139.QAA11604@mercury.xraylith.wisc.edu>; from Mumit Khan on Tue, Jun 15, 1999 at 04:39:06PM -0500 On Tue, Jun 15, 1999, Mumit Khan wrote: [...] > btw, I was perhaps a bit too harsh on -mno-cygwin, and possibly because > I don't have a clean solution to the "picking up wrong header and lib" > problem. One way of course is to use a combination of -nostdinc and > -idirafter <...> when -mno-cygwin is specified in the specs file, and > that might just work very well. Yep, there are pitfalls currently. We would like volunteers to help make the mingw support better, including submitting patches that make the source tree build libstdc++ without Cygwin as well as with. Some rewriting of the specs file may help this mode as well. Until this happens, people will run into problems unless they're careful. -- Geoffrey Noer Email: noer@cygnus.com Cygnus Solutions -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com