Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Fri, 25 Jan 2002 22:03:09 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: A cygwin hosted MinGW targeted cross platform
Message-ID: <20020126030309.GA4404@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3C51CCD2.5080009@ece.gatech.edu>
User-Agent: Mutt/1.3.23.1i

On Fri, Jan 25, 2002 at 04:23:30PM -0500, Charles Wilson wrote:
>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 was offering an example of the way Red Hat does things.

I actually got the above example wrong.  The real path that we use
is either

/usr/cygnus/H-i686-pc-cygwin/i686-pc-mingw32 (deprecated)

or (I think)

/usr/redat/H-i686-pc-cygwin/i686-pc-mingw32

or, possibly,

/opt/redhat/H-i686-pc-cygwin/i686-pc-mingw32

So, that wouldn't conflict with anything that Earnie is doing.  I don't
know that the H-whatever makes sense in this scenario but, like I said,
I was just offering an example.

Even if, for some reason, the decision was made to use /opt/redhat,
I can assure everyone that it is very very unlikely that Red Hat
will ever be offering a i686-pc-mingw32 cross compilation environment
in the GNUpro toolkit.

>I like /usr/cross, myself, so you could have /usr/cross/i686-pc-mingw, 
>/usr/cross/arm-v4l-linux, etc.

Actually, if Earnie follows anyone's advice in this thread, he'd end up
overwriting at least one user's layout.  If he uses something as
straightforward as /usr/cross, he'd probably end up overwriting more
than one.

If this proposal is for a standard cygwin package, then it should
just live in /usr/...  The mingw binaries go to
/usr/bin/i686-pc-mingw-{gdb,as,gcc}, gcc libraries in
/usr/lib/gcc-lib/i686-pc-mingw, and additional files in
/usr/i686-pc-mingw/....

Otherwise, if we want to avoid overwriting existing stuff, then
the only alternative is to use something like /usr/earnie_release/...
or something.

cgf

--
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/