From: Byron Stanoszek <gandalf@winds.org>
To: gcc@gcc.gnu.org
Subject: warning: pasting would not give a valid preprocessing token
Date: Fri, 11 Aug 2000 20:41:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0008112340220.6780-100000@winds.org> (raw)
I've seen this warning in many of my .c files when compiling with versions of
2.96 from mid-july and newer.. has anyone else seen this before, know what it
is, and how to fix it?
warning: pasting would not give a valid preprocessing token
--
Byron Stanoszek Ph: (330) 644-3059
Systems Programmer Fax: (330) 644-8110
Commercial Timesharing Inc. Email: bstanoszek@comtime.com
next reply other threads:[~2000-08-11 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-11 20:41 Byron Stanoszek [this message]
2000-08-11 20:46 ` Geoff Keating
2000-08-11 20:58 ` Byron Stanoszek
2000-08-11 23:31 ` Zack Weinberg
2000-08-12 8:19 ` Byron Stanoszek
2000-09-06 19:18 ` Zack Weinberg
2000-09-07 12:04 ` Byron Stanoszek
2000-09-11 21:44 ` Zack Weinberg
[not found] <20000914185040.A12722@daikokuya.demon.co.uk>
[not found] ` <Pine.LNX.4.21.0009141510140.21092-201000@winds.org>
2000-09-14 15:53 ` Neil Booth
2000-09-14 16:02 ` Neil Booth
2000-09-14 16:08 ` Jeffrey A Law
2000-09-15 16:53 ` Byron Stanoszek
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.21.0008112340220.6780-100000@winds.org \
--to=gandalf@winds.org \
--cc=gcc@gcc.gnu.org \
/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).