Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "Dave Korn" <dk AT artimi DOT com>
To: <cygwin AT cygwin DOT com>
Subject: RE: Problems building setup from CVS.
Date: Tue, 12 Oct 2004 16:26:42 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <ckgsbf$dbc$1@sea.gmane.org>
Message-ID: <NUTMEGAywrKiXVCWVPA000003ed@NUTMEG.CAM.ARTIMI.COM>
X-OriginalArrivalTime: 12 Oct 2004 15:26:42.0954 (UTC) FILETIME=[E09E36A0:01C4B06F]

> -----Original Message-----
> From: cygwin-owner On Behalf Of Hans Horn
> Sent: 12 October 2004 16:14

> Group,
> 
> did all the patches get checked-in that would allow to build 
> setup from cvs 
> ootb? coz it still doesn't build!
> If no, please do!

  Well, in the meantime, you can always apply the changes locally to your
own copy of the sources yourself.  They really are trivial.  You simply have
to delete six lines.  I don't know if they're suitable to check in as-is,
because then setup wouldn't build for anyone who still had the older version
of the w32api support files.  Presumably they should be wrapped in some kind
of ifdef-version check, but I don't know what exactly.


    cheers, 
      DaveK
-- 
Can't think of a witty .sigline today....


--
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/