public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c/7657: gcc.2.95.2 -O2 (for alpha)  loops endless in java/parse.c
Date: Tue, 20 Aug 2002 10:36:00 -0000	[thread overview]
Message-ID: <20020820171602.23675.qmail@sources.redhat.com> (raw)

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

From: Andrew Pinski <pinskia@physics.uc.edu>
To: wharms@bfs.de
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c/7657: gcc.2.95.2 -O2 (for alpha)  loops endless in java/parse.c
Date: Tue, 20 Aug 2002 13:13:04 -0400

 you should not be building gcc with just `make'.
 
 You should be building gcc with `make bootstrap'.
 
 
 Thanks,
 Andrew Pinski
 
 PS close this bug report because it is not using the recommended 
 way of building gcc.
 


             reply	other threads:[~2002-08-20 17:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 10:36 Andrew Pinski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-08-26  5:56 jsm28
2002-08-20  9:06 wharms

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=20020820171602.23675.qmail@sources.redhat.com \
    --to=pinskia@physics.uc.edu \
    --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: 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).