Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Fri, 17 Nov 2000 15:49:41 +0000 Message-ID: <4492-Fri17Nov2000154941+0000-starksb@ebi.ac.uk> X-Mailer: emacs 20.7.1 (via feedmail 9-beta-7 I); VM 6.75 under Emacs 20.7.1 From: David Starks-Browning MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: cygwin-developers AT cygwin DOT com Subject: Re: Error 1 and error 2 compiling winsup In-Reply-To: References: <4283-Fri17Nov2000104308+0000-starksb AT ebi DOT ac DOT uk> On Friday 17 Nov 00, Brian Keener writes: > One part might be a little unclear (at least for me) is the configure > line: > > /src/configure --prefix=/install -v > configure.log 2>&1 > > where it mentions /install. How does this relate to d:\cygwin or /usr > (ie the install path) where my cygwin is installed. I imagine the /install is to isolate the 'development build' from your working Cygwin environment. But it's a reasonable question, especially for the developers list, how to actually *use* what you build. Perhaps someone who actually does this can advise. If it were me, I'd probably keep them segragated, and use PATH to control which I was using. This could be cumbersome if you're testing inetd and need to change PATH in several places, or have Cygwin in your NT System Path. Hope this helps. David