-Original Message-
From: uclibc-boun...@uclibc.org [mailto:uclibc-boun...@uclibc.org] On
Behalf Of Natanael Copa
Sent: den 9 april 2010 10:08
To: Bernhard Reutner-Fischer
Cc: uclibc@uclibc.org
Subject: Re: problems with gnu make and stdout with uclibc nptl
On Thu, Apr 8, 2010 at
Peter Kjellerstedt wrote:
Unless it has changed in the last years, there are no expressed
guarantees regarding API and ABI stability for the 0.x.y releases of
uClibc. AFAIK the stable API/ABI is intended for the 1.0.0 release.
And with the upcoming integration of the NPTL support, I do not see
2010/4/12 Timo Teräs timo.te...@iki.fi:
Peter Kjellerstedt wrote:
Unless it has changed in the last years, there are no expressed guarantees
regarding API and ABI stability for the 0.x.y releases of uClibc. AFAIK the
stable API/ABI is intended for the 1.0.0 release. And with the upcoming
From: Timo Teräs timo.te...@iki.fi
NPTL defines errno as __thread variable. Define USE___THREAD so proper
errno assignment is used in assembly files.
This fixes segfault while building python.
Signed-off-by: Timo Teras timo.te...@iki.fi
Signed-off-by: Natanael Copa natanael.c...@gmail.com
---
On 04/12/2010 05:19 AM, Natanael Copa wrote:
From: Timo Teräs timo.te...@iki.fi
NPTL defines errno as __thread variable. Define USE___THREAD so proper
errno assignment is used in assembly files.
Thanks! Sorry I missed this flag when doing the port. Committed.
-Austin
Remove the -DUSE___THREAD from specific assembler files since its
used everywhere anyway.
This is a cleanup after 447a9d1cc181395c3e2ea77ea88e45dee4b30ce6
Signed-off-by: Natanael Copa natanael.c...@gmail.com
---
.../sysdeps/unix/sysv/linux/i386/Makefile.arch | 16 +---
1 files
Hi,
something is definitively wrong with stdio used in threads on x86.
I have enabled run-time assertions and run this phello.c on a multicore box:
#include pthread.h
#include stdio.h
void * printmsg(char *s){
printf(printmsg: %s\n, s);
return;
}
void pthread_hello(void)
{
On 04/12/2010 12:21 PM, Natanael Copa wrote:
Smells like stdio is not threads safe?
Interesting. I supposed there could be an issue with the libc internal futex
code that replaces the old use of pthread mutexes directly. We could verify this
with a bit of work by getting the old style mutexes to
Austin Foxley wrote:
On 04/12/2010 12:21 PM, Natanael Copa wrote:
Smells like stdio is not threads safe?
Interesting. I supposed there could be an issue with the libc internal futex
code that replaces the old use of pthread mutexes directly. We could verify this
with a bit of work by getting
