Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Tue, 16 Oct 2001 10:57:30 +0200 From: Corinna Vinschen To: Cygwin-Apps Subject: Re: problems compiling current cygwin cvs release Message-ID: <20011016105730.U1696@cygbert.vinschen.de> Mail-Followup-To: Cygwin-Apps References: <001101c15618$e43580c0$651c440a AT BRAMSCHE> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001101c15618$e43580c0$651c440a@BRAMSCHE>; from Ralf.Habacker@freenet.de on Tue, Oct 16, 2001 at 10:02:25AM +0200 On Tue, Oct 16, 2001 at 10:02:25AM +0200, Ralf Habacker wrote: > Some time ago I have found an instruction to configure the winsup tree. But > currently I can't find that information in the faq or user guide. > Can anyone tell me, how I can find this instruction. > My dir layout after checking out the whole cygwin src tree is: > [...] > Note that the i686-pc-cygwin dir is empty It will be filled after calling `make'. The target specific subdirectories are configured later in the `make' step. > Than I tried to configure winsup in a seperate build dir > 1. cd ~/cvs.cygwin.com > 2. mkdir wsbuild > 3. cd wsbuild > 4. ../src/winsup/configure That doesn't work. Your first configure has created everything needed by winsup. You should either call `make all-target-winsup' in the toplevel build dir or just don't build in the whole src directory but checkout only the relevant parts: cvs co winsup or, if you also want to build `dumper.exe': cvs co winsup naked-intl naked-bfd Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc.