RE: Is it a bug of PTHREAD_MUTEX_ERRORCHECK_NP ?

[Roland McGrath <roland redhat com>]

> # arm-linux-gcc -D_GNU_SOURCE -g -c tst-mutex2.c -I../sysdeps/pthread
> # arm-linux-gcc -g -o tst-mutex2 tst-mutex2.o libpthread.a clone.o 
> /glibc/setjmp/setjmp.o /glibc/setjmp/sigjmp.o /glibc/setjmp/bsd-setjmp.o 
> /glibc/setjmp/bsd-_setjmp.o /glibc/setjmp/longjmp.o 
> /glibc/setjmp/__longjmp.o  /glibc/setjmp/jmp-unwind.o                     
> /glibc/csu/libc-start.o -Wl,-M > tst-mutex2.map 2>&1
> 
> # arm-linux-gcc  -g -c tst-join1.c -I../sysdeps/pthread
> # arm-linux-gcc -g -o tst-join1 tst-join1.o libpthread.a clone.o 
> /glibc/setjmp/setjmp.o /glibc/setjmp/sigjmp.o /glibc/setjmp/bsd-setjmp.o 
> /glibc/setjmp/bsd-_setjmp.o /glibc/setjmp/longjmp.o 
> /glibc/setjmp/__longjmp.o  /glibc/setjmp/jmp-unwind.o                     
> /glibc/csu/libc-start.o -Wl,-M > tst-join1.map 2>&1

Ok, you are doing static linking with a bizarre manually chosen subset of
libc object files.  I won't worry about your problems unless you report
details about using a normal compilaton scheme.