Hi, On Tue, 2011-02-22 at 18:12 -0500, Mike Frysinger wrote: > On Wednesday, January 26, 2011 05:02:05 Alfeiks Kaänoken wrote: > > My first review of the existing sysdeps and other source code > > shows me that there are many linux-specific code (yes, > > I mean linux specific code that resides within non-os specific > > code). > > patches welcome. linuxisms should only exist under libc/sysdeps/linux/ for > the C library. it's right and not right, I can list here what I mean. Just for the first review check out librt, there are no sysdeps. Also you may find some linux specific code outside of the sysdeps in libc. > > > btw, the main difference with linux (or other monolithic OSes) is > > many OS functions (open() for example) aren't syscalls - it's > > RPC functions (yes, actually it will be a syscall that call IPC > > function to send an RPC message). In this case I need to > > find a better way to port it (i.e. without heavy modifications to > > keep uclibc sources tree more closely to the upstream one). > > Could you advice me something ? > > the linux syscalls should all live in libc/sysdeps/linux/ already, so if you > had libc/sysdeps/jari/, it should be OK. yep, we found that and place all Jari OS specific code in libc/sysdeps/jari, the same is true for the libpthreads (we use our existing one). Currently we are ported uclibc (yep, we don't put our IDL generated functions yet since we're doing refactoring of the existing interfaces). If you are interested I can give you a link to the git branch with ported uclibc. > -mike
Thanks, _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
