How the hell do i get rid of it?

I guess this is a warning from gcc? Be sure that any headers file are ending by an empty line, this is due assure source compatibility if you want to compile your sources with some very old C compiler that doesn't handle header files inclusion properly when they does not end by an empty newline...

1 members found this post helpful.

There's a standard thing you'll find. Going back to typewriter days, the m$dos system and successors did a carriage_return/line_feed. Linux just puts the return at the end of a line. There are utilities to swap around it. BTW, if you find yourself here, just be aware that this problem was licked in the 70s or early 80s and the solutions are many utilities that convert msods files to linux ones. You can even write a file and add carriage returns with sed or awk

If you have no return at all, and you want one, I think it's done off the terminal width. In vim, you can do this with
:set tw=80
or any chosen figure. My knowledge of vim, emacs, etc is also squat

1 members found this post helpful.

It seems completely stupid but i try to fix it.

These are the joys of 'reinventing the wheel'. If you have a clear vision how your system is going to differ, start a project. If not, forget it, as what you write now will be out of date by the time you have much assembled.

Or using your favorite text editor move the cursor to the end of the last line, past the last character and press the enter key. gcc expects an end of line character on every line but it sees an end of file marker.

1 members found this post helpful.