From: eclark <eclark@alabanza.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: problem with new kernel
Date: Fri, 30 Jun 2006 13:13:13 -0400 [thread overview]
Message-ID: <200606301313.13691.eclark@alabanza.com> (raw)
In-Reply-To: <1151685938.11434.51.camel@laptopd505.fenrus.org>
My apologies for the double email. For what its worth:
[root@dev linux-2.4.32]# getconf GNU_LIBPTHREAD_VERSION
NPTL 0.60
Not sure what that implies (other than its still broke. :| )
On Friday 30 June 2006 12:45 pm, Arjan van de Ven wrote:
> Hi,
>
> you're running a kernel without NPTL support on a distribution that
> apparently expects NPTL support to be in the kernel... the failure mode
> isn't nice but failure at all isn't totally unexpected...... NPTL is
> needed for certain functionality and if a distribution expects that to
> be there.. things may well go very wonky if absent. (yes glibc tries to
> emulate this but the emulation is quite limited and not really possible)
prev parent reply other threads:[~2006-06-30 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-30 14:46 problem with new kernel eclark
2006-06-30 16:45 ` Arjan van de Ven
2006-06-30 17:10 ` eclark
2006-06-30 17:22 ` Arjan van de Ven
2006-06-30 17:13 ` eclark [this message]
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=200606301313.13691.eclark@alabanza.com \
--to=eclark@alabanza.com \
--cc=arjan@infradead.org \
--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 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.