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 Date: Fri, 20 Apr 2001 14:50:20 -0400 From: Christopher Faylor To: Cygwin Apps Subject: Re: GCC -mno-cygwin vs mingw32-gcc cross environment. Message-ID: <20010420145020.A25768@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: Cygwin Apps References: <3AE07A27 DOT 3AAC7BE5 AT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AE07A27.3AAC7BE5@yahoo.com>; from earnie_boyd@yahoo.com on Fri, Apr 20, 2001 at 02:04:23PM -0400 On Fri, Apr 20, 2001 at 02:04:23PM -0400, Earnie Boyd wrote: >I've just successfully completed building a Cygwin native cross build >environment for --target=mingw32. While I'm cleaning up the code >modifications I would like to ask if we should consider deprecating the >-mno-cygwin switch in favor of the cross environment? > >I would rather see the cross build environment become standard because >it is a natural for autoconfiguration. You just add --host=mingw32 to >the configuration scripts instead of needing to do CC='gcc -mno-cygwin' >configure ... . > >Comments? Without gettin too much into the semantics of the word "deprecate", I think it makes sense to strongly discourage use of -mno-cygwin if there is a true cross-compiler available. So, are you proposing that you will maintain a i686-pc-mingw32-gcc port, Earnie? One problem is that this will mean keeping at least a separate version of binutils/ld, too, since ld has some builtin defaults that may not be appropriate for mingw. cgf