Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Date: Thu, 17 Jun 1999 11:54:46 -0400
From: cygwin AT sourceware DOT cygnus DOT com
To: Vadim Egorov <egorovv AT 1c DOT ru>
Cc: cygwin AT sourceware DOT cygnus DOT com
Subject: Re: yikes, what are these?
Message-ID: <19990617115446.A782@cygnus.com>
References: <199906162102 DOT RAA21060 AT jaj DOT com> <37688D3D DOT E572808C AT 1c DOT ru>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.3i
In-Reply-To: <37688D3D.E572808C@1c.ru>; from Vadim Egorov on Thu, Jun 17, 1999 at 09:53:01AM +0400

On Thu, Jun 17, 1999 at 09:53:01AM +0400, Vadim Egorov wrote:
>Hello,
>
>Yes, I had to build one of the recent egcs snapshots from sources but it
>was quite painless. I used Jan 15 cygwin snapshot -- it might have made 
>the trick -- and Mumit Khan's egcs-1.1.2 on the top of WinNT 4.0 sp5.  
>
>To have the same directory structure as clean B20.1 installation I run
>configure scripts using i586-cygwin32 as host parameter.

I thought I should point out something, since I have seen an apparent
misconception here a few times.

If you don't like the default structure that our cygwin releases impose on
you, there is no reason to use it.  Personally, I move everything around
to a more "UNIX-like" structure.  So, I have a /bin, /usr/bin, /usr/local/bin,
/usr/local/lib, etc.

What I'm trying to say, is that, with the possible exception of bison
(which will be fixed in the next release) nothing should be relying
on builtin path names using the funky H-*/i-* subdirectory structure.
Feel free to move things into more UNIX-friendly locations.

In fact, that's what we'll be doing in the next release.

-chris

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com