public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: David.Kernen@kernengroup.com
To: gcc-gnats@gcc.gnu.org
Subject: java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile
Date: Fri, 26 Jul 2002 08:36:00 -0000	[thread overview]
Message-ID: <20020726153312.4572.qmail@sources.redhat.com> (raw)


>Number:         7415
>Category:       java
>Synopsis:       gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 26 08:36:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Dave
>Release:        gcc-3.1
>Organization:
>Environment:
Sun/Solaris 2.6
>Description:
Make fails with "permission denied" errors trying to access
/home/mitchell/gcc/gcc-3.1/gcc-3.1/gcc/java/parse.c and 
parse-scan.c. 
>How-To-Repeat:
./configure ; make

or just vi the files!

If you have trouble figuring out what I'm talking about then
e-mail me (david.kernen@kernengroup.com) and I'll be happy
to send you a sample output file; however, the problem seems
pretty clear-cut to me and you've probably already fixed it 
anyway.
>Fix:
Edit the gcc-3.1/gcc/java/parse.c and parse-scan.c files to 
change the "/home/mitchell/..." path to the correct path and restart make. 
A relative path would also probably work.
>Release-Note:
>Audit-Trail:
>Unformatted:


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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-26  8:36 David.Kernen [this message]
2002-07-26  9:46 Tom Tromey
2003-01-29 20:12 aph

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=20020726153312.4572.qmail@sources.redhat.com \
    --to=david.kernen@kernengroup.com \
    --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).