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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 10 Apr 2003 19:14:50 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Vishal Jain cc: cygwin AT cygwin DOT com Subject: Re: Help!Unable to compile 1.3.22-1 sources In-Reply-To: <016401c2ffb5$018df840$b454893e@pomello> Message-ID: Importance: Normal MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Back when I compiled from source tarballs, I used a simpler approach: - Install sources for cygwin, w32api - cd /usr/src/cygwin-/winsup && ln -s /usr/src/w32api- w32api - cd /usr/src/cygwin- && mkdir build && cd build && configure where are the options from . I don't know why you'd need mingw... You *do* need bo build in a separate directory, though... Igor On Fri, 11 Apr 2003, Max Bowsher wrote: > Vishal Jain wrote: > > I had tried using the same steps mentioned below except that I didn't get > > the mingw separately. > > I am able to build w32api. > > It is failing in winsup/utils for me. > > Well, try the steps I mention exactly, because my test build just completed > OK. > > Max. > > > Vishal > > > >> From: "Max Bowsher" > >> To: "Vishal Jain" , > >> Subject: Re: Help!Unable to compile 1.3.22-1 sources > >> Date: Thu, 10 Apr 2003 23:44:18 +0100 > >> > >> Vishal Jain wrote: > >>> Thanks for looking into the problem. > >>> We need to get a stable version of cygwin to start with. Hence > >>> getting latest from CVS is not a good idea. > >> > >> Hmm. When I try building 1.3.22-1 from the tarball, I get the rather > >> perplexing error message: > >> > >> make[2]: *** No rule to make target `/usr/lib/w32api/Makefile', > >> needed by `/lib/'. Stop. > >> > >> But I can't figure out why make wants to make /usr/lib/w32api/Makefile. > >> > >> I suggest the following workaround. I haven't tested it, but intuition > >> suggests it should work. Here it is: > >> > >> tar jxvf path/to/cygwin-1.3.22-1-src.tar.bz2 > >> cd cygwin-1.3.22-1/winsup/ > >> tar jxvf path/to/w32api-2.3-1-src.tar.bz2 > >> mv w32api-2.3-1 w32api > >> tar jxvf path/to/mingw-runtime-2.4-1-src.tar.bz2 > >> mv mingw-runtime-2.4-1 mingw > >> cd ../.. > >> mkdir cygbuild > >> cd cygbuild > >> ../cygwin-1.3.22-1/configure > >> make > >> > >> Max. -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! Knowledge is an unending adventure at the edge of uncertainty. -- Leto II -- 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/