On Thu, Sep 18, 2008 at 5:05 PM, Carmelo AMOROSO [EMAIL PROTECTED]wrote:
Bernhard Reutner-Fischer wrote:
On Thu, Sep 18, 2008 at 03:29:09PM +0200, Carmelo AMOROSO wrote:
Absolutely agreed. IIRC I should now use __inline__ keyword, right?
yes.
Merged. Thanks for review ;-)
fails to
Fathi Boudra wrote:
On Thu, Sep 18, 2008 at 5:05 PM, Carmelo AMOROSO [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Bernhard Reutner-Fischer wrote:
On Thu, Sep 18, 2008 at 03:29:09PM +0200, Carmelo AMOROSO wrote:
Absolutely agreed. IIRC I should now use
fails to build on my config.
LD libuClibc-0.9.29.so http://libuClibc-0.9.29.so
libc/libc_so.a(posix_fadvise64.os): In function `posix_fadvise64':
posix_fadvise64.c:(.text+0x18): undefined reference to
`__illegally_sized_syscall_arg2'
posix_fadvise64.c:(.text+0x1c): undefined reference to
Fathi Boudra wrote:
fails to build on my config.
LD libuClibc-0.9.29.so http://libuClibc-0.9.29.so
http://libuClibc-0.9.29.so
libc/libc_so.a(posix_fadvise64.os): In function `posix_fadvise64':
posix_fadvise64.c:(.text+0x18): undefined reference
powerpc needs a specific implementation because it expects 8 bytes long
variable. Look recent messages, as I said, regarding pread_wirte
implementation.
I found a related patch submitted by wade berrier and commited by bernhard:
I'm trying to execute system( ) call (the one from stdlib.h) in an
application that requires uclibc5 and pthread lib both. System hangs up when
i do so.
Please help me out. Issue is resolves when I do not use pthread library.
Same function is working with uclibc4 with pthread library.
I tried
yogesh marathe wrote:
I'm trying to execute system( ) call (the one from stdlib.h) in an
application that requires uclibc5 and pthread lib both. System hangs up
when i do so.
Please help me out. Issue is resolves when I do not use pthread library.
Same function is working with uclibc4 with
I believe I have found the issue. Suppose there are threads A and B.
Thread A is running and is in the critical section of malloc() where
locks are held to manage the heap and such. A context switch then
occurs before thread A can relinquish the malloc locks. Thread B now
attempts to fork.
On Sep 19, 2008, at 4:05 PM, Chase N Douglas wrote:
I believe I have found the issue. Suppose there are threads A and B.
Thread A is running and is in the critical section of malloc() where
locks are held to manage the heap and such. A context switch then
occurs before thread A can
