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: <01b601c1a60e$c1523df0$0200a8c0@lifelesswks> From: "Robert Collins" To: "Charles Wilson" , References: <006601c1a5de$aa48b920$a300a8c0 AT nhv> <3C51C3B4 DOT 1F3A15F1 AT yahoo DOT com> <20020125205232 DOT GA32516 AT redhat DOT com> <3C51CCD2 DOT 5080009 AT ece DOT gatech DOT edu> Subject: Re: A cygwin hosted MinGW targeted cross platform Date: Sat, 26 Jan 2002 13:11:23 +1100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 26 Jan 2002 02:11:26.0708 (UTC) FILETIME=[C2906340:01C1A60E] === ----- Original Message ----- From: "Charles Wilson" > > > > 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 dunno, but maybe :}. FWIW, I usually place such things in /usr/local/ and then symlink binaries etc to /usr/local/bin. For a package, I'd have no objection to a mingw targeted gcc+binutils living in /usr/i686-pc-mingw/[bin|include|lib|share] > I like /usr/cross, myself, so you could have /usr/cross/i686-pc-mingw, > /usr/cross/arm-v4l-linux, etc. I'm impartial on this, but I wonder... what does the LSB and SFH (or whatever the layout standard is called) recommend for this? Rob -- 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/