Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com X-Apparently-From: Message-ID: <3AE0802E.60F0C811@yahoo.com> Date: Fri, 20 Apr 2001 14:30:06 -0400 From: Earnie Boyd Reply-To: Cygwin Apps X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: egor duda Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment. References: <3AE07A27 DOT 3AAC7BE5 AT yahoo DOT com> <97526857290 DOT 20010420221604 AT logos-m DOT ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit egor duda wrote: > > Hi! > > Friday, 20 April, 2001 Earnie Boyd earnie_boyd AT yahoo DOT com wrote: > > EB> I've just successfully completed building a Cygwin native cross build > EB> environment for --target=mingw32. While I'm cleaning up the code > EB> modifications I would like to ask if we should consider deprecating the > EB> -mno-cygwin switch in favor of the cross environment? > > EB> I would rather see the cross build environment become standard because > EB> it is a natural for autoconfiguration. You just add --host=mingw32 to > EB> the configuration scripts instead of needing to do CC='gcc -mno-cygwin' > EB> configure ... . > > EB> Comments? > > -mno-cygwin is currently used when building parts of cygwin itself. we > must be dealing with it somehow. > > i don't think we should deprecate -mno-cygwin (i believe it's quite > handy sometimes) but rather discourage using it when it's natural to > configure with --host=mingw32 > Perhaps this will help with understanding what I said: http://www.bartleby.com/61/54/D0145400.html I.E.: Deprecate != remove. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com