From: Jakub Jelinek <jakub@redhat.com>
To: Dinesh Ahuja <mdlinux7@yahoo.co.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Using the Native POSIX Threading Library (NPTL) instead of linuxthreads.
Date: Thu, 4 Mar 2004 05:00:06 -0500 [thread overview]
Message-ID: <20040304100006.GQ31589@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040304093805.18936.qmail@web8304.mail.in.yahoo.com>
On Thu, Mar 04, 2004 at 09:38:05AM +0000, Dinesh Ahuja wrote:
> Hi Everbody,
>
> I am new to Linux world and fascinated with it. I have
> an experience of 2.5 years in C++,C,COM,ATL,VC++ and
> want to get into Linux World.I have build and
> installed Linux Kernel 2.6.0 after struggling for four
> days.
>
> I installed Linux 2.6.0 so that I should be able to
> work with NPTL which is POSIX1.b compliant. But, when
> I see ma for mq_open and mq_close functions, it
> doesn't shows me anything.
NPTL doesn't support _POSIX_MESSAGE_PASSING yet, because the
kernel doesn't support it yet (patches are floating around though
and as soon as kernel starts supporting NPTL will add support
for it).
> How can I see the detailed descriptions of the
> services provided by NPTL ? Please suggest me what are
#include <unistd.h> and check the various _POSIX_* macros
(or browse /usr/include/{,nptl/}bits/posix_opt.h) or use sysconf/getconf
(for mq_* sysconf (_SC_MESSAGE_PASSING) or getconf MESSAGE_PASSING). See
http://www.opengroup.org/onlinepubs/007904975/basedefs/xbd_chap02.html
for details.
Jakub
next prev parent reply other threads:[~2004-03-04 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 9:38 Using the Native POSIX Threading Library (NPTL) instead of linuxthreads Dinesh Ahuja
2004-03-04 10:00 ` Jakub Jelinek [this message]
2004-03-04 13:25 ` Krzysztof Benedyczak
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=20040304100006.GQ31589@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdlinux7@yahoo.co.in \
/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