What flag silences GCC's warning about no new-line at file-endings?

Question

I just read this post about why new-line warnings exist, but to be honest my team has people working on several different platforms and with several different editors (everyone uses what bests suites them), so the warning has become ubiquitous, and since its not really a warning worth taking care of it's become Noise and makes finding serious warnings a hassle.

Many times important warnings have gone unnoticed because, people got used to having a gazillion useless warnings pass by, so they obviously just stop looking at them carefully, and with reason IMHO. One could say in our case GCC is crying wolf too much for anyone to take it seriously anymore, which is a bad attitude but its just human nature.

Right now we compile with -Wall, because we want warnings, but is there a counter flag to avoid the new-line warnings ?

Thanks in advance.

Note: I Looked through the manual a bit but didn't find the answer in any place obvious so I gave up.

Note: In response to Robert Gamble's totally reasonable solution, our code is cross-platform and we have people and builds on Linux, Solaris and Windows, so the new-line... is not under consensus. And Somebody's compiler is always going to cry-wolf. Because there are over 40 developers, and other non programmer staff as well.

Answer 1

Why don't you just make sure your files have a terminating newline like they are supposed to? This should be a simple configuration change in the offending editors and seems like a pretty easy way to "silence" the warning.

Answer 2

I'm 90% sure there is no arguemnt to turn this off.

The reason for the warning is that files without an endline give undefined behavior when compiled:

See standard: http://c0x.coding-guidelines.com/5.1.1.2.html

Here's a blog post with some python code (that I have not tried) which says it will fixup source files with this issue.

http://www.johndcook.com/blog/tag/gcc/

Answer 3

There isn't one as far as i know, i've used GCC for years.

Answer 4

Can someone enlight me? I'm using GCC 4.3.2, and compile with -Wall -pedantic -std=c89 and whatnot, but it keeps not outputting a warning about a missing newline, althought the file does not contain a newline at the end. I remember having read that warning in the past too.

FWIW, i too haven't found anything in the manpage of GCC.

[js@HOST2 cpp]$ cat file.c
#include "haha.h"
int main(void)
{

        return 0;
}[js@HOST2 cpp]$ cat haha.h
struct haha {
    int a;
};[js@HOST2 cpp]$ gcc -Wall file.c
[js@HOST2 cpp]$ gcc -Wall -pedantic -std=c89 -ansi file.c
[js@HOST2 cpp]$

What's going on?

Answer 5

See this SO question for more answers:

http://stackoverflow.com/questions/72271/no-newline-at-end-of-file-compiler-warning

Answer 6

Assuming you use some kind of source control system, you could add a pre-commit hook that ensures that text files end with a proper newline. Furthermore, depending on which source control system you use, you could add a pre-commit hook that actually fixes the line ending if it's not present.

Answer 7

Add a hook to your source control that won't allow successful code check-in until the newline is added?