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 Message-ID: <20020722144716.44135.qmail@web21005.mail.yahoo.com> Date: Mon, 22 Jul 2002 07:47:16 -0700 (PDT) From: Nicholas Wourms Subject: Re: [g++-3.1.1-4]: include flags still necessary to compile cygwin cvs (cygdaemon-branch) To: cygwin AT cygwin DOT com In-Reply-To: <20020722144218.GC4122@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Christopher Faylor wrote: > 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 " 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. > Thank you for clarifying that. I was under the [mistaken] impression that the new testing version had undergone some spec-file magic [which I had assumed was to correct this]. I suppose I'm thinking of something else. Sorry for the false alarm. Cheers, Nicholas __________________________________________________ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com -- 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/