Hi, all!
A tried to build uClibc r16550 for ARM920T OABI with NPTL and
discovered, that pthread_cancel
seems to work properly only for EABI, cause it calls libgcc_s functions
eg. _Unwind_Resume instead of _Unwind_SjLj_Resume, etc.,
and hence it fails
Does anybody have an idea?
--
Sergey Stasishin [EMAIL PROTECTED] writes:
A tried to build uClibc r16550 for ARM920T OABI with NPTL and
discovered, that pthread_cancel
seems to work properly only for EABI, cause it calls libgcc_s functions
eg. _Unwind_Resume instead of _Unwind_SjLj_Resume, etc.,
and hence it fails
On Wednesday 20 June 2007 15:36:21 Yann E. MORIN wrote:
Hello all!
On Thursday 24 May 2007 18:37, Yann E. MORIN wrote:
So, what about the patch I submitted few days ago (attached again)?
Hello? Any one cares to comment?
I haven't commented because I haven't encountered the bug this fixes.
Hello. Before making a bug report I want to check if any of you are familiar
with this... If I build uClibc with -O1, -O2, or -Os, and then statically
link a program to the new uClibc, the program will segfault. Dynamically
linked programs run fine, and if I build uClibc with -O0 both static
On Thursday 21 June 2007 16:07:14 Christian MICHON wrote:
On 6/21/07, Rob Landley [EMAIL PROTECTED] wrote:
Here's a video of an ex-debian maintainer (Martin Michlmayr, never heard
of him) giving Google a talk about the advantages of time based release
management.
(...)
Yes, I think
Hey Rob!
Hello All!
On Thursday 21 June 2007 21:52, Rob Landley wrote:
I haven't commented because I haven't encountered the bug this fixes. Lemme
see, it looks like if I build on i386, disable locale in uClibc, and use
2.6.21 make headers_install headers, will I see the bug? Or do I have
Hi,
We saw a problem like this in one of our PPC buildroot chains a some months
back. Do you know what version of uClibc you are using? I seem to vaguely
recall that we either upgraded our uClibc or used a compatability option to get
around it.
If no one else has a better answer I will
