From: Jeff Sturm <jsturm@one-point.com>
To: Paul Lim <paullimjh@hotmail.com>
Cc: gcc-help@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: Help : File does not end with newline
Date: Sun, 30 Sep 2001 09:44:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.10.10109301342300.14286-100000@mars.deadcafe.org> (raw)
In-Reply-To: <F20woYbq2qEACOU5cWM0000ea17@hotmail.com>
On Sun, 30 Sep 2001, Paul Lim wrote:
> However, I did not successful compile. The error message is
> diary.h:103: warning: file does not end in newline
This means the last few characters of diary.h are not a valid line
terminator, e.g. \n or \r\n.
> I am using gcc on Windows. Could OS be the problem?
Not directly. But Windows does seem to have a plethora of broken editor
software. Try to open/save this file in another source code editor, such
as emacs or even Windows Notepad.
Jeff
next prev parent reply other threads:[~2001-09-30 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-30 9:26 Paul Lim
2001-09-30 9:44 ` Jeff Sturm [this message]
2001-09-30 10:02 dewar
2001-09-30 14:47 ` Zack Weinberg
2001-09-30 17:44 Paul Lim
2001-09-30 18:21 ` Zack Weinberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.10.10109301342300.14286-100000@mars.deadcafe.org \
--to=jsturm@one-point.com \
--cc=gcc-help@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=paullimjh@hotmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).