[g++-3.1.1-4]: include flags still necessary to compile cygwin cvs (cygdaemon-branch)

[g++-3.1.1-4]: include flags still necessary to compile cygwin cvs (cygdaemon-branch)

[Nicholas Wourms]

Hi,

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.

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/

Re: [g++-3.1.1-4]: include flags still necessary to compile cygwin cvs (cygdaemon-branch)

[Christopher Faylor]

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/

Re: [g++-3.1.1-4]: include flags still necessary to compile cygwin cvs (cygdaemon-branch)

[Nicholas Wourms]

--- Christopher Faylor <cgf@redhat.com> 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 <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.
> 
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/