delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-developers/2002/07/12/15:16:52

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
Message-ID: <3D2F2B26.4040201@ece.gatech.edu>
Date: Fri, 12 Jul 2002 15:16:54 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4) Gecko/20011019 Netscape6/6.2
X-Accept-Language: en-us
MIME-Version: 1.0
To: Conrad Scott <Conrad DOT Scott AT dsl DOT pipex DOT com>
CC: cygwin-developers AT cygwin DOT com, Nicholas Wourms <nwourms AT netscape DOT net>
Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8
References: <20020711044304 DOT GA3292 AT redhat DOT com> <021001c229d2$e8f55b60$6132bc3e AT BABEL>


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 ]


No, not a good idea.  gcc-3.1.1-2 fixed this behavior, I think.  Plus, 
there's a gcc-3.1.1-3 coming out soon, so just chill, for now.  A g++ 
compiler that doesn't automatically include the directory where its own 
stdc++ library header files are stored is a broken g++ compiler and 
needs to be fixed in g++ itself -- not band-aiding every C++ program on 
earth.

--Chuck


- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019