Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Thu, 15 Jul 1999 13:29:26 -0400 To: Egor Duda Cc: "Suhaib M. Siddiqi" , cygwin-developers Subject: Re: gcc-2.95/ July 5 snapshot Message-ID: <19990715132926.A1102@cygnus.com> References: <8804 DOT 990715 AT logos-m DOT ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <8804.990715@logos-m.ru>; from Egor Duda on Thu, Jul 15, 1999 at 07:17:50PM +0400 What in the world does this have to do with the July 5 snapshot? How does changing a variable in the Makefile fix a problem with compiling winsup? Just to reiterate: Everyone should be building their stuff in a separate directory, i.e., don't build winsup in the same directory as the winsup sources. cgf On Thu, Jul 15, 1999 at 07:17:50PM +0400, Egor Duda wrote: >July, 15 1999, Suhaib M. Siddiqi wrote: > >SS> Trying to compile winsup-src (July 06 snapshot) with gcc-2.95. >SS> I hit the first bump ;-) Has anyone compiled a recent winsup-src >SS> with gcc-2.95? > >I've got the same problem with gcc-2.91.66 and previous versions. As a >quick workaround, i've just changed one line in winsup\Makefile.in from > >updir:= $(dir $(srcdir)) > >to > >updir:= $(srcdir)/../ > >and it works just fine.