I've got sel4test running with libsel4 not having a dependency on libc. I've pulled out libsel4assert, libsel4benchmark, libsel4printf and libsel4putchar from libsel4 and they are separate libraries

The biggest change is to seL4/libsel4 and  sel4/tools/bitfield_gen.py. The changes to bitfield_gen.py allow it to generate the same code as before for the kernel but uses the new names for entities in user space.

Please let me know what you think.

-- Wink


https://github.com/winksaville/seL4/tree/libsel4-no-libc-dependency
https://github.com/winksaville/libsel4test/tree/libsel4-no-libc-dependency
https://github.com/winksaville/libsel4allocman/tree/libsel4-no-libc-dependency
https://github.com/winksaville/libsel4utils/tree/libsel4-no-libc-dependency
https://github.com/winksaville/sel4test/tree/libsel4-no-libc-dependency
https://github.com/winksaville/libsel4assert
https://github.com/winksaville/libsel4benchmark
https://github.com/winksaville/libsel4printf
https://github.com/winksaville/libsel4putchar