public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: other/7773: compilation problem in gcc/java/parse*.c
@ 2002-12-13  4:43 reichelt
  0 siblings, 0 replies; 4+ messages in thread
From: reichelt @ 2002-12-13  4:43 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, lanclos, nobody

Synopsis: compilation problem in gcc/java/parse*.c

State-Changed-From-To: open->feedback
State-Changed-By: reichelt
State-Changed-When: Fri Dec 13 04:43:58 2002
State-Changed-Why:
    Does "gmake bootstrap" solve the problem for you?

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


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

* Re: other/7773: compilation problem in gcc/java/parse*.c
@ 2002-12-18 11:34 reichelt
  0 siblings, 0 replies; 4+ messages in thread
From: reichelt @ 2002-12-18 11:34 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, lanclos, nobody

Synopsis: compilation problem in gcc/java/parse*.c

State-Changed-From-To: feedback->closed
State-Changed-By: reichelt
State-Changed-When: Wed Dec 18 11:34:25 2002
State-Changed-Why:
    Cannot be reproduced anymore:
    
    > > Does "gmake bootstrap" solve the problem for you?
    > Presumably it would have. I tried re-running the compile again, but my
    > user environment has changed significantly in the intervening months,
    > and I cannot duplicate the problem.
    
    > If the solution is to run "gmake bootstrap", this begs the question
    > of why the default "make" for the Makefile does not simply summon
    > "gmake bootstrap".

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


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

* Re: other/7773: compilation problem in gcc/java/parse*.c
@ 2002-08-30 10:36 Andrew Pinski
  0 siblings, 0 replies; 4+ messages in thread
From: Andrew Pinski @ 2002-08-30 10:36 UTC (permalink / raw)
  To: nobody; +Cc: gcc-prs

The following reply was made to PR other/7773; it has been noted by GNATS.

From: Andrew Pinski <pinskia@physics.uc.edu>
To: lanclos@cats.ucsc.edu
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: other/7773: compilation problem in gcc/java/parse*.c
Date: Fri, 30 Aug 2002 13:28:15 -0400

 you are not using the correct way of compiling gcc, you should use 
 `gmake bootstrap'
 
 Thanks,
 Andrew Pinski
 
 On Friday, Aug 30, 2002, at 11:38 US/Eastern, lanclos@cats.ucsc.edu 
 wrote:
 
 > gmake
 


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

* other/7773: compilation problem in gcc/java/parse*.c
@ 2002-08-30  8:56 lanclos
  0 siblings, 0 replies; 4+ messages in thread
From: lanclos @ 2002-08-30  8:56 UTC (permalink / raw)
  To: gcc-gnats


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


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

end of thread, other threads:[~2002-12-18 19:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-12-13  4:43 other/7773: compilation problem in gcc/java/parse*.c reichelt
  -- strict thread matches above, loose matches on Subject: below --
2002-12-18 11:34 reichelt
2002-08-30 10:36 Andrew Pinski
2002-08-30  8:56 lanclos

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