Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Jun Sun <jsun@mvista.com>
Cc: Nicu Popovici <octavp@isratech.ro>, linux-mips@oss.sgi.com
Subject: Re: Cross_compiler!
Date: Tue, 14 Nov 2000 17:16:46 +0100	[thread overview]
Message-ID: <20001114171646.B1117@bacchus.dhis.org> (raw)
In-Reply-To: <3A103DAE.463492A4@mvista.com>; from jsun@mvista.com on Mon, Nov 13, 2000 at 11:14:54AM -0800

On Mon, Nov 13, 2000 at 11:14:54AM -0800, Jun Sun wrote:

> My weekend was just fine - without reading this bothersome email. :-)
> 
> I thought egcs-1.1.2 had some problems with binutil 2.8.1 and glibc
> 2.0.6.  Was the problem solved?  

Kindof.  I just dumped the multilib support.  I don't know of anybody who
was actually using it, so away with it ...

  Ralf

      reply	other threads:[~2000-11-14 18:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-08 23:13 Cross_compiler! Nicu Popovici
2000-11-08 19:47 ` Cross_compiler! Jun Sun
2000-11-08 20:05   ` Issues with R8000 nick
2000-11-08 20:05     ` nick
2000-11-12 20:10   ` Cross_compiler! Ralf Baechle
2000-11-13 19:14     ` Cross_compiler! Jun Sun
2000-11-14 16:16       ` Ralf Baechle [this message]

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=20001114171646.B1117@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=octavp@isratech.ro \
    /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