Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "Gleb O. Raiko" <raiko@niisi.msk.ru>
To: Florian Lohoff <flo@rfc822.org>
Cc: Ralf Baechle <ralf@oss.sgi.com>,
	linux-mips@oss.sgi.com, linux-mips@fnet.fr,
	linux-origin@oss.sgi.com
Subject: Re: libc upgrade
Date: Tue, 26 Sep 2000 12:37:57 +0400	[thread overview]
Message-ID: <39D06065.FC00C7A0@niisi.msk.ru> (raw)
In-Reply-To: 20000926010416.B3761@paradigm.rfc822.org

> > Ok, second theory.  What linker where you using to build all this programs?
> > The new ld.so needs to know what ld has built programs due to some pretty
> > stupid pre-2.9.something brokeness in R_MIPS_32 reloction handling.
> 
> egcs 1.0.3a binutils 2.8.1 (Very conservative)
> 

Well, another question. Ralf uploaded cross tools rpms year ago. Does
anybody have native rmps for big endian ? Also, does anybody have cross
tools for sparc glibc 2.1 (RH6.x sparc distribution) ? I can't compile
cross gcc on my Ultra, it seems like a bug in the sparc compiler, the
process fails in parsing an enum decl in a header.

Regards,
Gleb.

  parent reply	other threads:[~2000-09-26  8:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-22 13:26 libc upgrade Ralf Baechle
2000-09-25  9:24 ` Florian Lohoff
2000-09-25 11:20   ` Ralf Baechle
2000-09-25 14:15     ` Florian Lohoff
2000-09-25 20:14       ` Ralf Baechle
2000-09-25 23:04         ` Florian Lohoff
2000-09-26  0:46           ` Ralf Baechle
2000-09-26  8:37           ` Gleb O. Raiko [this message]
2000-09-26 10:36             ` Florian Lohoff
2000-09-26 21:06               ` Ralf Baechle
2000-09-26 17:48             ` Keith M Wesolowski
2000-09-26  8:30         ` Gleb O. Raiko
2000-09-26 22:47           ` 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=39D06065.FC00C7A0@niisi.msk.ru \
    --to=raiko@niisi.msk.ru \
    --cc=flo@rfc822.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=linux-origin@oss.sgi.com \
    --cc=ralf@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