Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT cygwin DOT com Delivered-To: mailing list cygwin-developers AT cygwin DOT com Message-ID: <02d601c229de$04d26110$6132bc3e@BABEL> From: "Conrad Scott" To: References: <20020711044304 DOT GA3292 AT redhat DOT com> <021001c229d2$e8f55b60$6132bc3e AT BABEL> <3D2F2B26 DOT 4040201 AT ece DOT gatech DOT edu> <20020712193712 DOT GD9546 AT redhat DOT com> Subject: Re: Available for test: gcc-3.1.1-2 gcc2-2.95.3-8 Date: Fri, 12 Jul 2002 20:55:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 "Christopher Faylor" wrote: > So, in this case adding the -I makes a certain sense. > Unfortunately, it means that we'll be adding one of > these for every version of the C compiler from 3.1.1 on, > which isn't right. > That is for gcc 3.2, we'll need a -I /usr/include/c++/3.2, etc. Yuck! I hadn't got quite that far in my thinking. > I'm not sure what the correct fix is for this. Seconded. > So, for now, I guess the only solution is to add the path > to the Makefile along with a big flashing FIXME. I think your points are enough to make me rip out that include and declare the new operator explicitly, which I believe is safe given that it's part of the C++ standard and shouldn't change *too* often [sic]. That way I can avoid the issue until someone comes up with decent solution. Of course, until it's solved, there'll also be no STL in the DLL or cygserver, but that might not be seen as a bad thing :-) // Conrad