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 Message-ID: <3C51CCD2.5080009@ece.gatech.edu> Date: Fri, 25 Jan 2002 16:23:30 -0500 From: Charles Wilson User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2 X-Accept-Language: en-us MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: A cygwin hosted MinGW targeted cross platform References: <006601c1a5de$aa48b920$a300a8c0 AT nhv> <3C51C3B4 DOT 1F3A15F1 AT yahoo DOT com> <20020125205232 DOT GA32516 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > Red Hat uses something like: > > /usr/H-i686-pc-cygwin > > for the cygwin "H"osted tools. > > Underneath that you get something like: > > i686-pc-cygwin > i686-pc-linux > etc. > > for the targeted tools. > > So, in this instance you'd have: > > /usr/H-i686-pc-cygwin/i686-pc-mingw32 Yeah, but don't we want to *avoid* colliding with the GNUpro stuff? If that's where Red Hat puts the various cygwin-hosted/other-target cross compilers that come with GNUpro, shouldn't we pick something ELSE? I like /usr/cross, myself, so you could have /usr/cross/i686-pc-mingw, /usr/cross/arm-v4l-linux, etc. --Chuck -- 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/