Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

[neil]

Synopsis: gcc 3.x cannot compile its own preprocessor output

State-Changed-From-To: open->feedback
State-Changed-By: neil
State-Changed-When: Tue Jun 18 03:38:46 2002
State-Changed-Why:
    Waiting for small testcase.  Thanks.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7040

Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

[neil]

Synopsis: gcc 3.x cannot compile its own preprocessor output

State-Changed-From-To: feedback->closed
State-Changed-By: neil
State-Changed-When: Mon Jun 24 13:46:29 2002
State-Changed-Why:
    Submitter cannot reproduce.  If you do reproduce this,
    I'd be happy to re-open this PR, or (more likely) fix
    it immediately.  However, my belief is that it was fixed
    between 3.0 and 3.0.4 sometime; I recall doing it.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7040

Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

[Thomas Dickey]

The following reply was made to PR preprocessor/7040; it has been noted by GNATS.

From: Thomas Dickey <dickey@herndon4.his.com>
To: neil@gcc.gnu.org, dickey@radix.net, gcc-bugs@gcc.gnu.org,
   gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output
Date: Fri, 21 Jun 2002 18:40:25 -0400

 --u3/rZRmxL6MmkK24
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 
 On Tue, Jun 18, 2002 at 10:38:46AM -0000, neil@gcc.gnu.org wrote:
 > Synopsis: gcc 3.x cannot compile its own preprocessor output
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: neil
 > State-Changed-When: Tue Jun 18 03:38:46 2002
 > State-Changed-Why:
 >     Waiting for small testcase.  Thanks.
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7040
 
 odd - rebuilding gcc 3.1 and 3.0.4 doesn't show the problem.  I had 3.0,
 3.0.4 and 3.1 installed in separate directories (but needed the space for
 another project).  So they should have been distinct/nonconflicting.
 
 fyi, attaching the wrappers I used for set environment, e.g.,
 	with-gcc-3.1 configure
 	with-gcc-3.1 make
 
 (I'll leave 3.1 installed for a while just in case ;-)
 
 -- 
 Thomas E. Dickey <dickey@invisible-island.net>
 http://invisible-island.net
 ftp://invisible-island.net
 
 --u3/rZRmxL6MmkK24
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="with-gcc-3.0"
 
 #!/bin/bash
 export TOP=/usr/local/gcc-3.0
 export PATH=$TOP/bin:$PATH
 export LD_LIBRARY_PATH=$TOP/lib:$TOP/lib/gcc-lib/i686-pc-linux-gnu/3.0:$LD_LIBRARY_PATH
 eval $*
 
 --u3/rZRmxL6MmkK24
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="with-gcc-3.0.4"
 
 #!/bin/bash
 export TOP=/usr/local/gcc-3.0.4
 export PATH=$TOP/bin:$PATH
 export LD_LIBRARY_PATH=$TOP/lib:$TOP/lib/gcc-lib/i686-pc-linux-gnu/3.0.4:$LD_LIBRARY_PATH
 eval $*
 
 --u3/rZRmxL6MmkK24
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="with-gcc-3.1"
 
 #!/bin/bash
 export TOP=/usr/local/gcc-3.1
 export PATH=$TOP/bin:$PATH
 export LD_LIBRARY_PATH=$TOP/lib:$TOP/lib/gcc-lib/i686-pc-linux-gnu/3.1:$LD_LIBRARY_PATH
 eval $*
 
 --u3/rZRmxL6MmkK24--

Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

[neil]

Synopsis: gcc 3.x cannot compile its own preprocessor output

State-Changed-From-To: feedback->open
State-Changed-By: neil
State-Changed-When: Sun Jun 16 14:36:54 2002
State-Changed-Why:
    In fact, I think 3.0.4 is fixed too.  Please let me know
    what you used; 3.x is not helpful.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7040

Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

[neil]

Synopsis: gcc 3.x cannot compile its own preprocessor output

State-Changed-From-To: open->feedback
State-Changed-By: neil
State-Changed-When: Sun Jun 16 14:35:52 2002
State-Changed-Why:
    Please confirm that this is fixed in 3.1.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=7040

preprocessor/7040: gcc 3.x cannot compile its own preprocessor output

[dickey]

>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: