public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile
@ 2002-07-26  9:46 Tom Tromey
  0 siblings, 0 replies; 3+ messages in thread
From: Tom Tromey @ 2002-07-26  9:46 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile
@ 2003-01-29 20:12 aph
  0 siblings, 0 replies; 3+ messages in thread
From: aph @ 2003-01-29 20:12 UTC (permalink / raw)
  To: David.Kernen, gcc-bugs, gcc-prs, java-prs, nobody

Synopsis: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile

State-Changed-From-To: open->closed
State-Changed-By: aph
State-Changed-When: Wed Jan 29 20:12:02 2003
State-Changed-Why:
    The build process generates parse.c and parse-scan.c.
    They are no longer included in the source tree at all.

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


^ permalink raw reply	[flat|nested] 3+ messages in thread

* java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile
@ 2002-07-26  8:36 David.Kernen
  0 siblings, 0 replies; 3+ messages in thread
From: David.Kernen @ 2002-07-26  8:36 UTC (permalink / raw)
  To: gcc-gnats


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


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-01-29 20:12 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-07-26  9:46 java/7415: gcc/java/parse.c and gcc/java/parse-scan.c require editing to compile Tom Tromey
  -- strict thread matches above, loose matches on Subject: below --
2003-01-29 20:12 aph
2002-07-26  8:36 David.Kernen

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).