Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 Message-ID: <00ce01c2ffa7$2bf20da0$b454893e@pomello> From: "Max Bowsher" To: "Vishal Jain" , References: Subject: Re: Help!Unable to compile 1.3.22-1 sources Date: Thu, 10 Apr 2003 22:19:49 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Vishal Jain wrote: > Hi, > If I use this tag, w32api-2_2, which cygwin release will it correspond to? > Is it ok to use this tag? No. > ----------------------------------------------------------------------- > Hi, > I am unable to compile 1.3.22-1 sources. It is failing while compiling > utils. > I have 2.3.1 w32api package sources which I believe is the latest. Yes, latest. BTW, the version is 2.3-1. Yes, I can figure out what you mean, but its still best to be correct. > Which version of w32api package shall I use? > > Is there a CVS label I can use to get 1.3.22-1 sources which are in sync > with w32api so that I can do a build. There are no public use CVS tags for Cygwin releases. Any tags you may find with CVSweb are private-use for the person preparing releases, and do not correspond exactly to the source tarball. I'm not quite sure what is failing. I'm downloading the source tarball now. When I need to build Cygwin, I usually build cvs HEAD. That's probably not a great idea at the moment, though, as the trunk is in the midst of the great 32/64 enablement. 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/