Mime-Version: 1.0 (Apple Message framework v752.3)
In-Reply-To: <46AA2EDD.51C16419@dessent.net>
References: <81B25FE9-8193-4731-8876-B54CED0BDE9D@zooko.com> <46AA2EDD.51C16419@dessent.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <99F719C4-1411-42DE-82D7-B934B69F4EF0@zooko.com>
Content-Transfer-Encoding: 7bit
From: zooko <zooko@zooko.com>
Subject: Re: how to build cygwin using itself
Date: Fri, 27 Jul 2007 12:42:14 -0600
To: cygwin@cygwin.com
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Jul 27, 2007, at 11:43 AM, Brian Dessent wrote:

> zooko wrote:
>
>> http://cygwin.com/cvs.html
>>
>> Which say to check out "winsup".
>
> That's your problem.  I'm not sure why that page says that, but just
> checking out winsup will give you a tree that can't be used to build
> anything.
>
>> Could someone give me a hint as to what other steps are necessary to
>> build cygwin using itself?
>
> "cvs co cygwin"

This doesn't work for me:

-------
$ CVSROOT=:pserver:anoncvs@cygwin.com:/cvs/src cvs co cygwin
cvs server: cannot find module `cygwin' - ignored
cvs [checkout aborted]: cannot expand modules
-------

Hm.  Looking at the CVS layout it appears that I might need "src/",  
which is the common parent of "winsup/" and "newlib/".

I'll try that.

...

Hm, I can see that this is going to take a long time to cvs co.  I'll  
report back later how it works.

Regards,

Zooko


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/