Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Florian Lohoff <flo@rfc822.org>
Cc: linux-mips@oss.sgi.com, linux-mips@fnet.fr, linux-origin@oss.sgi.com
Subject: Re: libc upgrade
Date: Mon, 25 Sep 2000 22:14:14 +0200	[thread overview]
Message-ID: <20000925221414.A6190@bacchus.dhis.org> (raw)
In-Reply-To: <20000925161500.A4773@paradigm.rfc822.org>; from flo@rfc822.org on Mon, Sep 25, 2000 at 04:15:00PM +0200

On Mon, Sep 25, 2000 at 04:15:00PM +0200, Florian Lohoff wrote:

> > > Build fails on mipsel ...
> > 
> > These messages look like file corruption.  Maybe one of the `features'
> > of the 2.4.0-test kernels and not libc at all?
> 
> I dont think so - I succeeded to compile ~2000 Packages of debian
> on this kernel and its noticeably the first execution with the "new" ld.so

I week of CPU time on an Origin building packages:  No problems ...  I'm
actually fairly close to get a RH 6.2 built - as far as that is possible
with glibc 2.0.

> LD_LIBRARY_PATH=..:../elf:../nss ../elf/ld.so.1 ./rpcgen -c rpcsvc/bootparam.x -o xbootparam.T
> /bin/sh: invalid character 45 in exportstr for full-config-sysdirs
> make[1]: *** [xbootparam.stmp] Segmentation fault

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.

  Ralf

  reply	other threads:[~2000-09-25 20:15 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 [this message]
2000-09-25 23:04         ` Florian Lohoff
2000-09-26  0:46           ` Ralf Baechle
2000-09-26  8:37           ` Gleb O. Raiko
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=20000925221414.A6190@bacchus.dhis.org \
    --to=ralf@oss.sgi.com \
    --cc=flo@rfc822.org \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=linux-origin@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