Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Mon, 22 Jul 2002 10:42:18 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: [g++-3.1.1-4]: include flags still necessary to compile cygwin cvs (cygdaemon-branch)
Message-ID:	<20020722144218.GC4122@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20020722125521 DOT 26243 DOT qmail AT web21010 DOT mail DOT yahoo DOT com>
Mime-Version:	1.0
In-Reply-To:	<20020722125521.26243.qmail@web21010.mail.yahoo.com>
User-Agent:	Mutt/1.3.23.1i

On Mon, Jul 22, 2002 at 05:55:21AM -0700, Nicholas Wourms wrote:
>I just wanted to report that I am still having to append: 
>
>"-I/usr/include/c++/3.1.1"
>
>when building the cygwin sources from the cygdaemon branch.  This is
>because one of the cygserver files uses "#include <new>" and for some
>reason g++ preprocessor isn't finding it properly.  However, everything is
>perfect once I pass the include flag.  I was under the impression you
>thought you had fixed this, so I thought it would be worthwile to inform
>you that this condition still exists.

And, so...?  We've already discussed why it is necessary to do this.  It
wasn't anticipated that a new release of gcc would magically fix the
problem.  There is no way that it could.

cgf

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

- Raw text -