Waldemar Brodkorb
b8fcdddcbb
nios2: sync support with glibc
|
%!s(int64=10) %!d(string=hai) anos | |
|---|---|---|
| .. | ||
| alpha | %!s(int64=10) %!d(string=hai) anos | |
| arc | %!s(int64=9) %!d(string=hai) anos | |
| arm | %!s(int64=10) %!d(string=hai) anos | |
| avr32 | %!s(int64=10) %!d(string=hai) anos | |
| bfin | %!s(int64=10) %!d(string=hai) anos | |
| c6x | %!s(int64=10) %!d(string=hai) anos | |
| common | %!s(int64=10) %!d(string=hai) anos | |
| common-generic | %!s(int64=13) %!d(string=hai) anos | |
| cris | %!s(int64=10) %!d(string=hai) anos | |
| frv | %!s(int64=10) %!d(string=hai) anos | |
| h8300 | %!s(int64=10) %!d(string=hai) anos | |
| hppa | %!s(int64=10) %!d(string=hai) anos | |
| i386 | %!s(int64=10) %!d(string=hai) anos | |
| ia64 | %!s(int64=10) %!d(string=hai) anos | |
| lm32 | %!s(int64=10) %!d(string=hai) anos | |
| m68k | %!s(int64=10) %!d(string=hai) anos | |
| metag | %!s(int64=10) %!d(string=hai) anos | |
| microblaze | %!s(int64=9) %!d(string=hai) anos | |
| mips | %!s(int64=10) %!d(string=hai) anos | |
| nds32 | %!s(int64=10) %!d(string=hai) anos | |
| nios2 | %!s(int64=9) %!d(string=hai) anos | |
| or1k | %!s(int64=10) %!d(string=hai) anos | |
| powerpc | %!s(int64=9) %!d(string=hai) anos | |
| sh | %!s(int64=10) %!d(string=hai) anos | |
| sparc | %!s(int64=10) %!d(string=hai) anos | |
| x86_64 | %!s(int64=10) %!d(string=hai) anos | |
| xtensa | %!s(int64=10) %!d(string=hai) anos | |
| Makefile | %!s(int64=21) %!d(string=hai) anos | |
| Makefile.commonarch | %!s(int64=11) %!d(string=hai) anos | |
| Makefile.in | %!s(int64=17) %!d(string=hai) anos | |
| README | %!s(int64=13) %!d(string=hai) anos | |
README
This directory level abstracts out the Linux Operating System dependent
features of uClibc for supported Linux architectures/CPUs. If you wanted to
port uClibc to some new Linux architecture (arm, mips, etc), this is the place
to add that support.
All stuff that is not at all dependent on a particular Linux architecture
goes in the 'common' directory. However, for new architectures which are
using the generic syscalls in the Linux Kernel, the 'common-generic'
directory should be used instead as they all use identical interfaces for
the system calls.
features of uClibc for supported Linux architectures/CPUs. If you wanted to
port uClibc to some new Linux architecture (arm, mips, etc), this is the place
to add that support.
All stuff that is not at all dependent on a particular Linux architecture
goes in the 'common' directory. However, for new architectures which are
using the generic syscalls in the Linux Kernel, the 'common-generic'
directory should be used instead as they all use identical interfaces for
the system calls.