uclibc-ng

Fork

Oops. Forgot this one....

These are now obsolete

Fix up sig handling so it is more in sync with glibc behavior

Bring these into line with glibc 2.2.4

This header file was broken, breaking signal handling on ARM.
This update fixes it...
-Erik

In theory, this adds readdir64 and friends. Dunno if they
work yet or not....
-Erik

This commit makes large file support actually work (when enabled in
the config file). I've tested this and it works for me.
-Erik

Fix comment

Geez, I really screwed that one up. Lets try that one again...
Revert mmap to where it was in rev 1.41 of this file,
-Erik

Oops. I merged things backwards. Lets try that again...

Revert global old mmap usage, and do it per arch

Disable posix threads support

depend on kernel-headers, not kernel-headers-2.4

Merged patch from pre-glibc-2.2.4 files

include/bits from glibc-2.2.4-1

Turn off program_invocation_name and friend

Erwin Authried <eauth@softsys.co.at> noticed that _XOPEN_SOURCE is
supposed to be a number

Beef up the fork test, checking for proper SIGCHLD behavior

A small patch from Erwin Authried <eauth@softsys.co.at>
*) changed ARM crt0.S / crt0pic.S selection -- depends on DOPIC now.
*) Minor tweek to syscall definitions

Fix problem with version naming

Little script to create a properly-named snapshot for Debian packaging

Fixes for finding appropriate kernel headers, changelog entry

Add missing values.h

Add strndup, written by Stefan Soucek <ssoucek@coactive.com>

Patch from Miles Bader <miles@lsi.nec.co.jp> to support the v850.
He sent this patch to me a month ago, but I forgot to apply it...

Minor update

Wohoo! David McCullough found the bug! His comments follow:

I had a look at it and you won't believe it was always broken.

I'll try and explain it, let me know if it doesn't make sense.

* ash calls setjmp, which messes with the stack to look like it has
two args instead of one and then jmps (actually falls) into
sigsetjmp.

BUG

* sigsetjmp then saves the registers and "jumps" to __sigset_save, a C
function.

BUG1 - because the caller pops its args off the stack, a program that
changes it's number of args is broken because the caller will
not
pop the correct number of args.

I think that jumping from the sigsetjmp asm to the 'C' code is unsafe
but I can't think of an example. Anyway, I have attached what I think
is
a working fix.

The reason this worked without -fomit-frame-pointer is that the
_sigset_save 'C' code would restore the stack pointer from %ebp (the
frame
pointer) and because none of the asm had moded it, when we returned
from
__sigset_save the stack was back to it's correct position for 1
argument
despite our best attempts to stuff it up ;-)

Yet more minor cleanups

Patch from David McCullough <davidm@lineo.com>:

* reduce the sigset types to 32 bits (I've mentioned this before)
I think I saw this change go in for another platform anyway ;-)

* Do not use _IO_FILE as it clashes with the C++ libraries which know
too much about how glibc workds :-(

* Do not use _G_va_list for the same reason.

* remove the CTORS/DTORS from crt0.S for ARM as the compiler provided
crtbegin.o and crtend.o have these (and only these) already in them and
you get multiple defined errs :-(

With all the headerfile changes, some functions didn't get there arg types
fixed up.