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: <3D2F335C.20409@ece.gatech.edu> Date: Fri, 12 Jul 2002 15:51:56 -0400 From: Charles Wilson 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: cygwin-developers AT cygwin DOT com 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> <3D2F2B26 DOT 4040201 AT ece DOT gatech DOT edu> <20020712193712 DOT GD9546 AT redhat DOT com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Christopher Faylor wrote: > > So, for now, I guess the only solution is to add the path to the > Makefile along with a big flashing FIXME. You'd still need a big flashing FIXME, but what about computing the path from gcc -v? GCCVER=`(gcc -v 2>&1) | grep "^gcc version" | awk '{print $3}'` GCCINC=-I/usr/include/c++/$(GCCVER) > > I wonder why "they" are making so many tweaks to the header file stuff > in 3.1. It seems a little to severe to be part of a minor version > number release. Yep. "They" are really pesky. --Chuck