Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT 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 <cabbey AT bresnanlink DOT net>
X-Sender:	cabbey AT tweedle DOT cabbey DOT net
To:	DJ Delorie <dj AT delorie DOT com>
cc:	cygwin AT cygwin DOT com
Subject:	Re: setup.exe ==> source directory mess (?)
In-Reply-To:	<200103090600.BAA10888@envy.delorie.com>
Message-ID:	<Pine.LNX.4.21.0103091133370.25063-100000@tweedle.cabbey.net>
MIME-Version:	1.0

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

- Raw text -