Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Fri, 10 Oct 2003 15:26:50 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Can't build cygwin from CVS: configure error Message-ID: <20031010192650.GD4771@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3F86ACC7 DOT 90803 AT student DOT tue DOT nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Oct 10, 2003 at 09:10:03PM +0200, Hannu E K Nevalainen wrote: >> From: Micha Nelissen >> Sent: Friday, October 10, 2003 2:58 PM > >> Hi, >> >> Can somebody help me with this problem while making cygwin: >> > >> >> Any hints appreciated! >> >> Micha. >> > >May I guess that you did the same as I did, i.e. follow the instructions on >cvs page... Then you need THIS information too: > >from http://cygwin.com/contrib.html > >_Building the development version of Cygwin_ > >Note that minimally, the top-level source tree needs to contain: > >Makefile.in, config, config-ml.in, config.guess, config.sub, configure, >configure.in, include, install-sh, libiberty, ltconfig, ltmain.sh, missing, >move-if-change, newlib, symlink-tree, winsup, ylwrap. > > >... and note that "/src/configure" in the FAQ seems to reference this -^ >configure. So, I think I'm hearing some sort of bug report here that the cvs 'winsup' module does not include the correct files but, as usual, it is difficult to tell since the message is, as always, couched in the "you should do this to fix the problem rather than making it hard for everyone" language rather than including a simple statement of what, exactly is wrong. -- 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/