All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicu Popovici <octavp@isratech.ro>
To: Christoph Martin <martin@uni-mainz.de>
Cc: ralf@oss.sgi.com, Christoph.Martin@uni-mainz.de,
	linux-mips@oss.sgi.com, linux-mips@fnet.fr,
	debian-mips@lists.debian.org, Andreas Jaeger <aj@suse.de>
Subject: Re: glibc 2.2 on MIPS
Date: Fri, 05 Jan 2001 11:38:27 -0500	[thread overview]
Message-ID: <3A55F882.4B693DE3@isratech.ro> (raw)
In-Reply-To: 14932.57412.617757.439688@arthur.zdv.Uni-Mainz.DE

[-- Attachment #1: Type: text/plain, Size: 1855 bytes --]

Hello all,

My question is somehow related on the problems showed in this email. Sorry if this
will bother you.
I am trying to setup a cross toolchain for mips and  I have to use binutils 2.10
and gcc 2.95.2 and glibc2.1.3. Currently I am trying to setup binutils 2.10 with
egcs1.0.3a and with glibc.2.0.6 . Do you have any patches for binutils 2.10 or for
gcc2.95.2 for mips ? If you have and if you have some ideeas please tell me ..

Thank You
Nicu

Christoph Martin wrote:

> Hi Ralf,
>
> On Thu, 12 Oct 2000 04:04:44 +0200, Ralf Baechle wrote:
>
> > On Thu, Oct 12, 2000 at 12:24:21AM +0200, Florian Lohoff wrote:
>
> > > 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.
>
> > There patch is ok; you get those bus errors because there are bugs in
> > both ld and binutils that in most cases compensate each other.  If you
> > fix only one of them you get all sorts of funnies ...
>
> I just tried to build glibc-2.2 (CVS-2000-12-28) for debian-mips and
> it still has the "Bus Error" problem. We are currently using binutils
> 2.10.1.0.2 and gcc 2.95.2 + CVS from 2.95 branch.
>
> Can you please post both patches, so that we can verify which one is
> missing in our build.
>
> > Even with the fixes ld is not yet perfect - for example emacs and X still
> > fail.
>
> The gcc/binutils combination seams to work correctly as far as I can
> see. I managed to compile xfree 4.0.2 linked agains 2.1.95-1.1. What
> problems did you have with X?
>
> Christoph

[-- Attachment #2: Card for Nicu Popovici --]
[-- Type: text/x-vcard, Size: 259 bytes --]

begin:vcard 
n:POPOVICI;Nicolae Octavian 
tel;cell:+40 93 605020
x-mozilla-html:FALSE
org:SC Silicon Service SRL;Software
adr:;;;;;;
version:2.1
email;internet:octavp@isratech.ro
title:Software engineer
x-mozilla-cpt:;0
fn:Nicolae Octavian POPOVICI
end:vcard

  parent reply	other threads:[~2001-01-05  8:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 20:42 glibc 2.2 on MIPS Christoph Martin
2001-01-04 21:34 ` Maciej W. Rozycki
2001-02-01  9:27   ` Geert Uytterhoeven
2001-02-01 12:38     ` Maciej W. Rozycki
2001-02-01 15:15       ` Geert Uytterhoeven
2001-02-01 15:30         ` Maciej W. Rozycki
2001-02-01 15:48           ` Geert Uytterhoeven
2001-01-05 16:38 ` Nicu Popovici [this message]
2001-01-05 10:29   ` Christoph Martin
2001-01-05 23:03 ` Nicu Popovici
2001-01-05 21:10   ` Christoph Martin

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=3A55F882.4B693DE3@isratech.ro \
    --to=octavp@isratech.ro \
    --cc=Christoph.Martin@uni-mainz.de \
    --cc=aj@suse.de \
    --cc=debian-mips@lists.debian.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=martin@uni-mainz.de \
    --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.