Available for test: gcc-3.1.1-2 gcc2-2.95.3-8

Christopher Faylor cgf@redhat.com
Fri Jul 12 13:16:00 GMT 2002

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}'`

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++.


More information about the Cygwin-developers mailing list