delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT cygwin DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT cygwin DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT cygwin DOT com> |
List-Help: | <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT cygwin DOT com |
Delivered-To: | mailing list cygwin-developers AT cygwin DOT com |
Date: | Fri, 12 Jul 2002 15:13:37 -0400 |
From: | Christopher Faylor <cgf AT redhat DOT com> |
To: | cygwin-developers AT cygwin DOT com |
Subject: | Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 |
Message-ID: | <20020712191337.GE9109@redhat.com> |
Reply-To: | cygwin-developers AT cygwin DOT com |
Mail-Followup-To: | cygwin-developers AT cygwin DOT com |
References: | <20020711044304 DOT GA3292 AT redhat DOT com> <021001c229d2$e8f55b60$6132bc3e AT BABEL> |
Mime-Version: | 1.0 |
In-Reply-To: | <021001c229d2$e8f55b60$6132bc3e@BABEL> |
User-Agent: | Mutt/1.3.23.1i |
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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |