On Wednesday 08 April 2009 23:44:07 Dan E wrote: > ---------- patch start ----------
posting patches inline meant for direct inclusion really only works when: - it's only 1 patch - patch is at the end of the e-mail multiple patches should either be separate e-mails or attached. there should also be a short description of each one individually. > --- uClibc-nptl/include/unistd.h (revision 26031) > +++ uClibc-nptl/include/unistd.h (working copy) > -extern void __exit_thread (int val) __attribute__ ((noreturn)); > +extern void __exit_thread (int val) __attribute__ ((__noreturn__)); for changes clearly not related to NPTL, these should go into trunk and split out of any NPTL-specific changes. > --- uClibc-nptl/libc/signal/sigpause.c (revision 26031) > +++ uClibc-nptl/libc/signal/sigpause.c (working copy) > +#include <string.h> for changes not related to your arch let alone NPTL, you should be describing exactly why it's needed. a simple copy & paste of a compile error usually suffices. -mike
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc
