Re: V3 PATCH to aclocal.m4

[Jason Merrill <jason_merrill at redhat dot com>]

>>>>> "Benjamin" == Benjamin Kosnik <bkoz@redhat.com> writes:

> 1) aclocal is autogenerated. Patch acinclude.m4

Mea culpa.

> 2) there is only one file that need the backwards includes for building, 
> and it has a special rule just so we don't have to cart around backwards 
> includes for everything.
> 3) testsuite_flags.in  is what is used to export includes for non-library 
> use, like say the g++ testsuite. Perhaps you need this modified:

Actually, I started out modifying testsuite_flags.in, and then thought it
should go in aclocal.  If you think otherwise, I'll happily move it back.

> Perhaps you could explain the problem you've found? I strongly encourage 
> the use of standards-conformant headers in the g++ testsuite, if this is 
> the issue.

For most tests, I agree.  But we should also be able to test backward
compatibility.  And the installed compiler includes the backward headers,
so running it out of the build tree should too.

I use the compiler out of the build tree as my usual compiler, and use
testsuite_flags to provide the invocation flags.  I would like it to behave
like the installed compiler.

Jason