All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@linuxcare.com>
To: Andreas Thienemann <andreas@thienemann.net>
Cc: parisc-linux@parisc-linux.org
Subject: Re: [parisc-linux] Problems with glibc
Date: 20 Apr 2001 20:10:50 +0200	[thread overview]
Message-ID: <d3itjzfnmd.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: Andreas Thienemann's message of "Fri, 20 Apr 2001 19:10:43 +0200 (CEST)"

>>>>> "Andreas" == Andreas Thienemann <andreas@thienemann.net> writes:

Andreas> Has anyone ever experienced a similar problem? This segfault
Andreas> is reproducable and it's the first time that happened. gcc
Andreas> did compile correct, the same with the kernel itself.
Andreas> Therefore I'd guess that glibc is at fault here.  This
Andreas> happened while building the glibc on the hppa box (with the
Andreas> baseplus-20010404 nfsroot).  Building the cross-compiler
Andreas> toolchain which does include building glibc was successful
Andreas> though.

You don't see it when cross compiling because this is only run when
building natively. The sunrpc stuff is the first place where the newly
generated dynamic linker is exercised, your cross compiled binaries
are unlike to work either. The can be either a glibc (most likely
ld.so) or due to a change in syscall or compiler ABI behavior.

Jes

  reply	other threads:[~2001-04-20 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-20 17:10 [parisc-linux] Problems with glibc Andreas Thienemann
2001-04-20 18:10 ` Jes Sorensen [this message]
2001-04-22 19:20 ` Matthew Wilcox
2001-04-23 19:33   ` Andreas Thienemann

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=d3itjzfnmd.fsf@lxplus015.cern.ch \
    --to=jes@linuxcare.com \
    --cc=andreas@thienemann.net \
    --cc=parisc-linux@parisc-linux.org \
    /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.