From: Francis Galiegue <fg@mandrakesoft.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Pagesize bug vs. libpthread bug :(
Date: Mon, 12 Feb 2001 12:03:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590693005132@msgid-missing> (raw)
I've succeeded in compiling and installing the CVS version of glibc dated
20010208, but since then all programs using libpthread segfault. This includes
all fileutils, among others. Fortunately I have a "stable" glibc installed in
my chroot and so can export LD_LIBRARY_PATH to point to them, so my system is
still usable.
But that won't solve at all this pagesize problem. Hence my question: is there a
patch somewhere that makes programs linked statically with libnss work (hence
rpm) applying over *stock* glibc 2.2? I hate to have to choose between two
bugs, but I'd rather have ls, mv, etc work... And I'm not knowledgeable about
glibc internals at all...
Please help :(
--
Francis Galiegue, fg@mandrakesoft.com - Normand et fier de l'être
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race" -- R. Cook
reply other threads:[~2001-02-12 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=marc-linux-ia64-105590693005132@msgid-missing \
--to=fg@mandrakesoft.com \
--cc=linux-ia64@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox