Re: [Fwd: Bug#63511 acknowledged by developer(Bug#63511: fixed in glibc 2.2-7)]
>>"Eray" == Eray Ozkural (exa) <email@example.com> writes:
Eray> I'm sending this mail because libc maintainer seems to have closed
Eray> the bug I've issued without doing any investigation on his own.
Eray> libc6-dev: PTHREAD_ERRORCHECK_INITIALIZER_NP not defined as claimed in docs
Eray> The preprocessor macro seems to be undefined. There are also other
Eray> subtleties while using pthread lib, such as the __USE_UNIX_98 stuff,
Eray> which I really don't know (I only use c++, and UNIX_98 sections don't
Eray> seem to come along. Why is that?)
You do know what the _NP means, don't you? It stands for NON
PORTABLE. A conforming POSIX implementation is not required to
provide it. And glibc does not. Indeed, the standard does not seem to
even refer to this macro, at first reading: it is not in the indices,
so this is definitely a very implementation dependent macro. (If you
disagree, please quote chapter and verse from the standard).
Indeed, you should feel lucky that even the non standard
PTHREAD_ERRORCHECK_MUTEX_INITIALIZER_NP is provided by the
implementation, even though not present in ISO/IEC 9945-1
> Peter Palfrader wrote:
> > Did you do this first?
> No. I'm sending it here because I want it to be seen.
Wanted to make an ass of yourself in public, eh?
Who in the name of God would bring a half-eaten eight-ounce jar of
Hellman's mayonnaise to a public meeting? Tom Wolfe, "Bonfire of the
Manoj Srivastava <firstname.lastname@example.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C