Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Brady Brown <bbrown@ti.com>
To: SGI news group <linux-mips@oss.sgi.com>
Subject: egcs 1.0.3a build error?
Date: Tue, 14 Nov 2000 16:12:05 -0700	[thread overview]
Message-ID: <3A11C6C5.C2CAB92E@ti.com> (raw)

I am trying to natively build egcs-1.0.3a-2 on an Atlas board (r4kc
little endian). I followed the emails and pulled down
ftp://ftp.mvista.com/pub/Area51/mips_le/misc/egcs-10.03a.tar.gz and
ftp://oss.sgi.com/pub/linux/mips/egcs/egcs-1.0.3a-2.diff.gz
applied the diff and did configure and then make. (I'm running
binutils-2.8.1 glibc-2.0.6 and egcs-1.0.2). The build fails with this
output:

/tmp/cca30501.s: Assembler messages:
/tmp/cca30501.s:136: Internal error!
Assertion failure in mips_emit_delays at ./config/tc-mips.c line 2231.
Please report this bug.
make[1]: *** [xexit.o] Error 1
make: *** [all-target-libiberty] Error 2

I have been unable to figure out what the problem is.

Any ideas?

             reply	other threads:[~2000-11-14 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-14 23:12 Brady Brown [this message]
     [not found] <3A12F036.40753275@ti.com>
2000-11-15 20:33 ` egcs 1.0.3a build error? Ian Chilton
2000-11-16  1:57   ` Ralf Baechle

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=3A11C6C5.C2CAB92E@ti.com \
    --to=bbrown@ti.com \
    --cc=linux-mips@oss.sgi.com \
    /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