Re: How do I run "make check" in gcc with libstdc++-v3?

[Zack Weinberg <zack at wolery dot cumb dot org>]

On Tue, May 16, 2000 at 12:19:39AM -0500, Loren James Rittle wrote:
> 
> I'm not sure your patch is really working for you since you are still
> seeing many errors related to #include_next usage (you reported this
> in another message recently).  The only ways I see to get rid of those
> failures is (1) to find libstdc++-v3 headers with -isystem instead of
> -I while testing [good luck finding the right order for -isystem
> arguments given the current interactions with -B]

I just had an idea.  System-header-ness can be forced on with #line,
sort of - you'd write

#line 2 "header.h" 3

at the very top of the file, and that *should* suppress -pedantic
warnings in the rest of the file.  This is not suitable for general
use because (a) it's an obscure extension, and (b) it means errors in
the rest of the file will not carry information about the path to the
file (so e.g. emacs compilation-mode won't be able to find it).  But
we could have a thingy that just forced system-header-ness on and
didn't do anything else: something like #pragma system_header is
probably the appropriate interface.

What do people think of this idea?  It is absolutely trivial to
implement if we like it.  It can be rejected in the primary source
file, which would prevent most of the abuses I can think of right now.

zw