All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Jun Sun <jsun@mvista.com>,
	linux-mips@oss.sgi.com, linux-mips@fnet.fr,
	debian-mips@lists.debian.org
Subject: Re: glibc on MIPS ...
Date: Thu, 12 Oct 2000 00:24:21 +0200	[thread overview]
Message-ID: <20001012002421.A678@paradigm.rfc822.org> (raw)
In-Reply-To: <20001011041244.C7458@bacchus.dhis.org>; from ralf@oss.sgi.com on Wed, Oct 11, 2000 at 04:12:44AM +0200

On Wed, Oct 11, 2000 at 04:12:44AM +0200, Ralf Baechle wrote:
> On Tue, Oct 10, 2000 at 07:30:16PM -0700, Jun Sun wrote:
> > I also heard about the debian-mips project.  What glibc is used here?
> 
> A pre-2.2 snapshot.  Not yet stable and requires a binutils snapshot to
> build which also isn't yet stable.  But we're getting closer and things
> are beginning to look promising.

We are trying :) I am currently basing all my Debian-mips(el) things
on glibc 2.0.6. It is the only stable solution right now. I am experimenting
with the glibc 2.1.94-3 debian source package which i managed to get
compiled with unmodified cvs binutils and gcc + the gcse patch.

Ralf reported bugs in the ld where he send me a patch. With that patch
i get a "Bus Error" from the ld.so within the glibc build.

So currently - No real work on glibc 2.2 based debian but that will
change soon i guess ...

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5201-669912
      "Write only memory - Oops. Time for my medication again ..."

  parent reply	other threads:[~2000-10-11 22:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-11  2:30 glibc on MIPS Jun Sun
2000-10-11  2:12 ` Ralf Baechle
2000-10-11 11:06   ` Maciej W. Rozycki
2000-10-11 22:24   ` Florian Lohoff [this message]
2000-10-12  2:04     ` 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=20001012002421.A678@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=debian-mips@lists.debian.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.