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 Message-ID: <030701c2eccf$b01e8210$d351893e@pomello> From: "Max Bowsher" To: , "Rolf Campbell" References: <20030312173132 DOT C16261C221 AT redhat DOT com> <20030313075151 DOT GC26766 AT redhat DOT com> <20030313190504 DOT GB1808 AT redhat DOT com> Subject: Re: [ANNOUNCEMENT] Updated: cygwin-1.3.21-1 Date: Mon, 17 Mar 2003 21:50:17 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Rolf Campbell wrote: > Ok, had some time to look at this, but got stuck trying to get the DLL > to build on my maching (never tried this before). So, I downloaded the > cygwin-1.3.21-1 src. Is that package supposed to build OOTB? Interesting question. No one really cares about building from the cygwin source tarballs, because they prefer to build from cvs, because building from source tarballs is broken, because no one really cares about building from the cygwin source tarballs, because they prefer to build from cvs, ...... and so on ..... > I ran "./configure" > And then "make" > > tiswctype.c ..linked > twctrans.c ..linked > twctype.c ..linked > wctype.exp ..linked > loading cache ../config.cache > configure: error: can not find install-sh or install.sh in .. ./.. > make: *** [configure-target-newlib] Error 1 Hmm - it seems that configuring in the same directory as configure is broken, because no one does that .... you get the idea. OK, so: tar jxvf cygwin-1.3.21-1-src.tar.bz2 mkdir build cd build ../cygwin-1.3.21-1/configure make and, it breaks because winsup/w32api is missing. That's because that is the w32api package, released seperately. So install that package in the relevant place in the source tree? Well, no, because no released version of w32api is sufficiently up-to-date to build cygwin 1.3.21-1. Ouch. So, you should probably build from a cvs checkout. It will make your life easier. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/