Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Wed, 20 Feb 2002 01:27:45 +0100 From: Edouard Gomez To: cygwin AT cygwin DOT com Subject: Re: BUG with 1.3.9 : -mno-cygwin target still depends on cygwin1.dll Message-ID: <20020220002745.GA547@wanadoo.fr> References: <3c72e52d3d0da4b8 AT mel-rta3 DOT wanadoo DOT fr> <021e01c1b9a2$65ceb290$0100a8c0 AT advent02> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <021e01c1b9a2$65ceb290$0100a8c0@advent02> User-Agent: Mutt/1.3.27i Chris January (chris AT atomice DOT net) wrote: > It seems libtool is not passing the -mno-cygwin flag through when it starts > linking the DLL. > > Regards > Chris > I forgot to say one important thing : Before we fixed some bugs to the code, the libtool was close to produce a cygwin independant library. The linker was failing because it didn't find some common symbols in C like : stricmp strcmp and ... But now it's not even able to produce this error :\ Btw, how can i pass the -mno-cygwin option to the libtool with the help of autoconf ? Is there a special macro (i didn't find one in the autotools book from red hat) ? Regards -- Edouard Gomez -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/