From: Jerry Cooperstein <coop@axian.com>
To: Frank Cusack <fcusack@fcusack.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: NPTL v userland v LT (RH9+custom kernel problem)
Date: 07 Aug 2003 09:42:36 -0500 [thread overview]
Message-ID: <1060267356.1604.10.camel@p3.coop.hom> (raw)
In-Reply-To: <20030807013930.A26426@google.com>
If you read the release notes for RH9 you'll see you can adjust what
thread library gets used with the environmental variable
LD_ASSUME_KERNEL. So for instance you can do:
LD_ASSUME_KERNEL=2.2.5 rpm ....
LD_ASSUME_KERNEL=2.2.5 up2date
(I've mentioned these two because I've noted these fail when you are
root...)
======================================================================
Jerry Cooperstein, Senior Consultant, <coop@axian.com>
Axian, Inc., Software Consulting and Training
4800 SW Griffith Dr., Ste. 202, Beaverton, OR 97005 USA
http://www.axian.com/
====================================================================
On Thu, 2003-08-07 at 03:39, Frank Cusack wrote:
> Hi,
>
> The RH9 kernels have NPTL patches. Standard 2.4.21 does not.
> I am running a custom kernel without the NPTL stuff.
>
.....
>
> So, finally getting to my question, should I even *expect* a non-NPTL
> kernel to work with the RH9 userland? If not, is there a simple fix
> without going to NPTL, say just rebuilding glibc? hmm... now that I
> ask it I feel dumb, I do think I would need to rebuild glibc so it
> knows the kernel has LinuxThreads, not NPTL. OK, if that's true
> are there any other libs I should need to rebuild?
>
> thanks
next prev parent reply other threads:[~2003-08-07 14:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 8:39 Frank Cusack
2003-08-07 8:49 ` Arjan van de Ven
2003-08-07 14:42 ` Jerry Cooperstein [this message]
2003-08-07 13:06 ` Mathias Fröhlich
2003-08-08 5:45 ` Frank Cusack
2003-08-08 6:02 ` Valdis.Kletnieks
2003-08-08 6:53 ` Peter Svensson
2003-08-08 7:10 ` Pau Aliagas
2003-08-08 10:32 ` Henning P. Schmiedehausen
2003-08-08 17:37 ` Frank Cusack
2003-08-08 19:05 ` Ulrich Drepper
2003-08-07 13:20 Luke Howard
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=1060267356.1604.10.camel@p3.coop.hom \
--to=coop@axian.com \
--cc=fcusack@fcusack.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®