All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karsten Merker <karsten@excalibur.cologne.de>
To: linux-mips@oss.sgi.com, debian-mips@lists.debian.org
Subject: ls from fileutils-4.0.43 segfaults
Date: Sun, 22 Apr 2001 22:40:18 +0200	[thread overview]
Message-ID: <20010422224018.A9017@excalibur.cologne.de> (raw)

Hallo everyone,

I have tried to install fileutils_4.0.43-1_mipsel.deb from
source.rfc822.org and found that "ls" segfaults, the other binaries seem
to be ok. So I have tried compiling it myself against glibc-2.2.2 on
repeat.rfc822.org and also on my DECstation, but the effect stays the
same.

On repeat we have:
bash> ld -v
GNU ld version 2.11.90.0.1 (with BFD 2.11.90.0.1)
bash> gcc -v
gcc version 2.95.3 20010315 (Debian release)

On my DECstation I have:
bash> ld -v
GNU ld version 010330 (with BFD 010330)
bash> gcc -v
gcc version 2.95.3 20010315 (Debian release)

Has anybody successfully build fileutils-4.0.43 against glibc-2.2.2?

I had fileutils built ok against glibc-2.0.6 before with 
bash> gcc -v
Reading specs from /usr/lib/gcc-lib/mipsel-linux/egcs-2.90.29/specs
gcc version egcs-2.90.29 980515 (egcs-1.0.3 release)
bash> ld -v
GNU ld version 2.8.1 (with BFD 2.8.1)
(these contain Ralf's patches).

Greetings,
Karsten
-- 
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.

             reply	other threads:[~2001-04-22 20:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-22 20:40 Karsten Merker [this message]
2001-04-22 21:43 ` ls from fileutils-4.0.43 segfaults Daniel Jacobowitz
2001-04-23 18:14   ` Karsten Merker
2001-04-23  4:33 ` Keith M Wesolowski

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=20010422224018.A9017@excalibur.cologne.de \
    --to=karsten@excalibur.cologne.de \
    --cc=debian-mips@lists.debian.org \
    --cc=linux-mips@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.