public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Malcolm Purvis <malcolmpurvis@optushome.com.au>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/6275: Assembler errors building libjava/java/lang/Class.java.
Date: Sat, 13 Apr 2002 00:16:00 -0000	[thread overview]
Message-ID: <20020413071601.17426.qmail@sources.redhat.com> (raw)

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

From: Malcolm Purvis <malcolmpurvis@optushome.com.au>
To: sirl@gcc.gnu.org
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org,
   gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/6275: Assembler errors building
 libjava/java/lang/Class.java.
Date: Sat, 13 Apr 2002 17:13:46 +1000

 >>>>> "sirl" == sirl  <sirl@gcc.gnu.org> writes:
 
 sirl> State-Changed-Why: Update your binutils package to 2.11.93.0.2 or later
 sirl> and try again.
 
 With this version 'make bootstrap' now succeeds.  Thanks.
 
 However, the section of install.texi concerning my environment reads:
 
          @heading @anchor{powerpc-*-linux-gnu*}powerpc-*-linux-gnu*
 
          You will need
          @uref{ftp://ftp.varesearch.com/pub/support/hjl/binutils,,binutils 2.9.4.0.8}
          or newer for a working GCC@.  It is strongly recommended to recompile binutils
          if you initially built it with gcc-2.7.2.x.
 
 I believe that my existing system complied with these requirements.
 
 Malcolm
 
 -- 
 	       Malcolm Purvis <malcolmpurvis@optushome.com.au>
 
 The hidden, terrible cost of nuclear warfare is Really Bad Public Art.
 			        - Angus McIntyre, alt.peeves, 13/3/02.
 


             reply	other threads:[~2002-04-13  7:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-13  0:16 Malcolm Purvis [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-26 11:20 bangerth
2002-04-12  9:51 sirl
2002-04-12  6:46 malcolmpurvis

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=20020413071601.17426.qmail@sources.redhat.com \
    --to=malcolmpurvis@optushome.com.au \
    --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).