X-Spam-Check-By: sourceware.org Date: Thu, 26 Jan 2006 10:12:07 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Building Cygwin from CVS Message-ID: <20060126091207.GS8318@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <43CE88C6.3070009@hones.org.uk> <43D12B2C.23DD92C8@dessent.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Jan 25 20:41, Joshua Daniel Franklin wrote: > On 1/20/06, Brian Dessent wrote: > > Joshua Daniel Franklin wrote: > > > > > gcc make binutils cocom dejagnu > > > > gcc depends on binutils, so there's no need to list it as requirement. > > Perl is used in the build process as well. > > > > http://cygwin.com/ml/cygwin/2005-01/msg01266.html > > Thanks Brian, I think I saved that email somewhere since it was > informative, but never acted on it. :( > > I've added this info to > http://cygwin.com/faq/faq.programming.html#faq.programming.building-cygwin > and I'd like to put it in a winsup/README file but didn't want > to touch the top-level without some discussion. Does that sound OK to do? Yes, we can add a winsup/README if you want to do this. Would you mind to create a winsup README which basically follows the layout of the newlib README? That would be cool. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/