public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile Date: Fri, 26 Jul 2002 09:46:00 -0000 [thread overview] Message-ID: <20020726164602.2774.qmail@sources.redhat.com> (raw) The following reply was made to PR java/7415; it has been noted by GNATS. From: Tom Tromey <tromey@redhat.com> To: David.Kernen@kernengroup.com Cc: gcc-gnats@gcc.gnu.org, Mark Mitchell <mitchell@mail.codesourcery.com> Subject: Re: java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile Date: 26 Jul 2002 10:42:41 -0600 >>>>> "David" == David Kernen <David.Kernen@kernengroup.com> writes: David> Make fails with "permission denied" errors trying to access David> /home/mitchell/gcc/gcc-3.1/gcc-3.1/gcc/java/parse.c and David> parse-scan.c. Please send the exact error message. David> Edit the gcc-3.1/gcc/java/parse.c and parse-scan.c files to David> change the "/home/mitchell/..." path to the correct path and David> restart make. A relative path would also probably work. I agree that a full path pointing to Mark's home directory is probably not ideal. Maybe this is a fixable artifact of the release process? In any case, though, this is a bit odd. I think the paths in the parse*.c files ought to be used for debugging info only. Tom
next reply other threads:[~2002-07-26 16:46 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-26 9:46 Tom Tromey [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-29 20:12 aph 2002-07-26 8:36 David.Kernen
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=20020726164602.2774.qmail@sources.redhat.com \ --to=tromey@redhat.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).