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 16:16:51 -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: <20020712201651.GA11948@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> <3D2F2B26 DOT 4040201 AT ece DOT gatech DOT edu> <20020712193712 DOT GD9546 AT redhat DOT com> <3D2F335C DOT 20409 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3D2F335C.20409@ece.gatech.edu>
User-Agent: Mutt/1.3.23.1i

On Fri, Jul 12, 2002 at 03:51:56PM -0400, Charles Wilson wrote:
>
>
>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 was thinking about that but that would be second-guessing the include
directory structure.  Also, now that I think of it, it's not going to be
/usr/include/c++/3.1.1 for a cross compiler.  It will be something like
/usr/i686-pc-cygwin/include/c++/3.1.1 .

We could parse the include directories from something like:

  gcc -v -xc -E /dev/null

but then I have to wonder what benefit -nosdinc++ is giving us.  It
was supposed to avoid cross-pollination between the source sandbox
and the installed compiler but it seems to be causing more trouble
than it is worth.

Maybe the safest thing to do is to just drop -nostdinc++.

cgf