X-Spam-Check-By: sourceware.org
Message-ID: <43CE8CF3.375BB3B3@dessent.net>
Date: Wed, 18 Jan 2006 10:46:11 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Building Cygwin from CVS
References: <43CE88C6 DOT 3070009 AT hones DOT org DOT uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Cliff Hones wrote:

>   . It would be useful to mention in the FAQ which packages need to be installed
>     to perform the build.  I expect everyone will realise make, gcc, binutils etc.
>     are required, but I found I needed cocom (for shilka) which I'd not come across
>     before, and dejagnu in order to run the tests.

Since the generated devices.cc is stored in CVS you shouldn't need
shilka unless you modify devices.{in.h}.

>   . When I ran the tests, I got five unexpected failures (devdsp,
>     msgtest, pthread-cancel1, semtest and shmtest).  Is this to
>     be expected :-).

I would expect them to fail if you don't have cygserver installed and
running.

Brian

--
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/