Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sources.redhat.com Delivered-To: mailing list cygwin@sources.redhat.com X-Authentication-Warning: tweedle.cabbey.net: cabbey owned process doing -bs Date: Fri, 9 Mar 2001 11:44:28 -0600 (CST) From: Christopher Abbey X-Sender: cabbey@tweedle.cabbey.net To: DJ Delorie cc: cygwin@cygwin.com Subject: Re: setup.exe ==> source directory mess (?) In-Reply-To: <200103090600.BAA10888@envy.delorie.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Today, DJ Delorie wrote: > The correct way to build cygwin is from the top: > > mkdir /oss/bld > cd /oss/bld > /oss/src/configure (this is the directory that has winsup, newlib, libiberty, etc sources) this is effectively what I did. based on the chang you made to my path you must have assumed that the cygwin in there was the same cygwin that came from the cvs image... it isn't. The path to install.cc for example is /oss/src/cygwin/src/winsup/cinstall/install.cc /oss/src/cygwin is where I did the cvs co to begin with (last october) and the cvs update -Pd yesterday. So when I ran /oss/src/cygwin/src/configure I was running the script you suggest. It did not configure libiberty in /oss/bld/cygwin. (sorry about the confusion, but /oss/src has a couple dozen different projects' sources in it, and /oss/bld has just as many build trees - if not more.) -- now the forces of openness have a powerful and unexpected new ally - http://ibm.com/linux -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple