public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Thomas Dickey <dickey@herndon4.his.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: preprocessor/7040: gcc 3.x cannot compile its own preprocessor output Date: Fri, 21 Jun 2002 17:53:00 -0000 [thread overview] Message-ID: <20020621224603.12550.qmail@sources.redhat.com> (raw) 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--
next reply other threads:[~2002-06-21 22:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-21 17:53 Thomas Dickey [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-06-24 14:46 neil 2002-06-18 4:36 neil 2002-06-16 14:57 neil 2002-06-16 14:37 neil 2002-06-15 10:46 dickey
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=20020621224603.12550.qmail@sources.redhat.com \ --to=dickey@herndon4.his.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).