On Wed, Jul 30, 2008 at 02:46:04PM +0200, Michal Simek wrote: >Hi everybody, > >I have some question about Microblaze support in uClibc. >I look at Config.in and there is set BROKEN flags next to Microblaze label. >Can someone explain me what does it mean? What is broken?
$ svn log -r12209 extra/Configs/Config.in ------------------------------------------------------------------------ r12209 | vapier | 2005-11-11 04:06:13 +0100 (Fri, 11 Nov 2005) | 1 line mark all broken arches as such so people know not to expect too much ------------------------------------------------------------------------ Sounds like it's not actively maintained. Patches are welcome.. > >Microblaze community use 0.9.27 version and I would like to upgrade to >latest version and fix all bugs which are in Microblaze part. > >and next question I have is about supporting *nat syscalls (openat, mknodat >and others). Do you have any plan to add it? I do some changes on ancient >0.9.27 version and I do some test with it. I think uClibc should support >them. > >And then I look at kernel source and compare it with libc declaration. I >think that parameters should be the same. >For example on mknod call. And others. Please correct me if I am wrong. > >static __inline__ _syscall3(int, __syscall_mknod, const char *, path, > __kernel_mode_t, mode, __kernel_dev_t, dev); > >static __inline__ _syscall3(int, __syscall_mknod, const char *, path, > __kernel_mode_t, mode, unsigned, dev); Please look at the current version of sysdeps/linux/common/mknod.c for details. _______________________________________________ uClibc mailing list [email protected] http://busybox.net/cgi-bin/mailman/listinfo/uclibc
