public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dickey@radix.net
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output
Date: Sat, 15 Jun 2002 10:46:00 -0000	[thread overview]
Message-ID: <20020615151703.23994.qmail@sources.redhat.com> (raw)


>Number:         7040
>Category:       preprocessor
>Synopsis:       gcc 3.x cannot compile its own preprocessor output
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 15 08:26:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Thomas Dickey
>Release:        3.x (previously reported in pre-release of 3.0)
>Organization:
>Environment:
Linux (probably any platform)
>Description:
Using the -C preprocessor option causes the preprocessor to
generate an output file which cannot be compiled.  First
observed in the 2.96.x versions, the problem is that some
of the retained comments are passed through to the output
file's preprocessor lines, e.g., "#line", and the compiler
refuses to accept that.  Something as simple as a
"#endif /* foo */" can trigger this behavior.
>How-To-Repeat:
Try building lynx with the HTMLized config file, e.g.,
configure --enable-htmlized-cfg
>Fix:
I worked around this originally by removing comments from
some of lynx's header files.  However, glibc also has
comments in preprocessor lines.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-06-15 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 10:46 dickey [this message]
2002-06-16 14:37 neil
2002-06-16 14:57 neil
2002-06-18  4:36 neil
2002-06-21 17:53 Thomas Dickey
2002-06-24 14:46 neil

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=20020615151703.23994.qmail@sources.redhat.com \
    --to=dickey@radix.net \
    --cc=gcc-gnats@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).