[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Using gnulib with -pedantic, I get many warnings about #include_next

From: Reuben Thomas
Subject: Re: Using gnulib with -pedantic, I get many warnings about #include_next
Date: Sun, 24 Aug 2008 22:52:20 +0100 (BST)
User-agent: Alpine 1.00 (DEB 882 2007-12-20)

On Sun, 24 Aug 2008, Bruno Haible wrote:


Reuben Thomas wrote:
I compile my code with -pedantic, because I want it to work with compilers
other than GCC. This means that my compiler output is littered with warnings
about #include_next.

gnulib is clever enough to use #include_next only with compilers that support it
(i.e. gcc and Tru64 cc), but gcc does not know about it... So just ignore
this warning.

But it's noise and obscures genuine warnings and errors. I make my code compile without warnings both so that it is more likely to be correct, and so that I can easily identify warnings worth chasing in compiler output.

How can I stop this?

You could ask the GCC developers for an explicit control of the particular

This wouldn't help much: I don't want the warning suppressed, as I said, in non-third-party code. So it'd need some way for gnulib to turn it off, and gnulib would then have to use it. I admit this isn't so likely.

Or you can filter out the warnings that you don't like.

And as I said, that's tedious. I have to remember to do it, and I have to do it in multiple contexts (command-line, Emacs, ...).

Or you can use "rerun make" instead of "make". 'rerun' is a command which
outputs not the entire output of a command, but only the diffs compared to
its last run. This is useful when commands produce a lot of output.

Sounds interesting, but I can't find it. Have you a pointer to where this comes from? I can't find it in any obvious place.

http://rrt.sc3d.org/ | That's about as useful as a paper wok

reply via email to

[Prev in Thread] Current Thread [Next in Thread]