This is the mail archive of the
cygwin-developers@cygwin.com
mailing list for the Cygwin project.
Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
- From: Christopher Faylor <cgf at redhat dot com>
- To: cygwin-developers at cygwin dot com
- Date: Fri, 12 Jul 2002 15:13:37 -0400
- Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
- References: <20020711044304.GA3292@redhat.com> <021001c229d2$e8f55b60$6132bc3e@BABEL>
- Reply-to: cygwin-developers at cygwin dot com
On Fri, Jul 12, 2002 at 07:35:33PM +0100, Conrad Scott wrote:
>There's a problem compiling the cygwin_daemon branch with the gcc
>3.1.1 compiler as Nicholas discovered today. In particular, gcc
>can't find the <new> header file, which I need for the placement
>new operator. This used to be in /usr/lib/gcc-lib/.../include/
>but is now in /usr/include/c++/3.1.1/. Can I add this include
>path to the makefile now? I can't see that it'll break anything
>with gcc 2.X (as this include directory didn't exist previously).
>
>[Nb. In case something has changed here, note that I'm using other
>than the latest release of the gcc 3.1.1 compiler:
> gcc 3.1.1-1
> gcc-mingw 3_1-20020516-1 ]
I'd prefer finding out why g++ can't find the header file if
it is in /usr/include/c++/3.1.1. It is supposed to search the
path automatically.
Adding an included path should not be necessary. g++ -v should
tell you why it can't find new.
Just to be really clear: If you find that you need to add an include
path for something, that's a bug. You certainly shouldn't have to do
something special to find standard header files.
cgf