public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: lanclos@cats.ucsc.edu To: gcc-gnats@gcc.gnu.org Subject: other/7773: compilation problem in gcc/java/parse*.c Date: Fri, 30 Aug 2002 08:56:00 -0000 [thread overview] Message-ID: <20020830153834.28927.qmail@sources.redhat.com> (raw) >Number: 7773 >Category: other >Synopsis: compilation problem in gcc/java/parse*.c >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Aug 30 08:46:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: lanclos@cats.ucsc.edu >Release: gcc-3.2 >Organization: >Environment: Solaris 2.6, gcc 2.95.2, bison 1.35, binutils 2.13 >Description: Both parse.c and parse-scan.c, after running configure, contain lots of references to /home/mitchell/yaddayadda/parse.y that cause failures at compile-time. >How-To-Repeat: Download source tarball. Unpack. On a Solaris 2.6 SPARC machine (or potentially others, don't know), run a 'configure --prefix=/my/favorite/gcc-3.2; gmake', wait for a bit, and look for the errors whining about /home/mitchell to come spilling out. >Fix: Gloabal replace of /home/mitchell/yaddayadda/parse.y with the correct local absolute path for parse.y. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-08-30 15:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-30 8:56 lanclos [this message] 2002-08-30 10:36 Andrew Pinski 2002-12-13 4:43 reichelt 2002-12-18 11:34 reichelt
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=20020830153834.28927.qmail@sources.redhat.com \ --to=lanclos@cats.ucsc.edu \ --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: 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).