On Mon, Mar 21, 2011 at 10:24 AM, Waldemar Brodkorb wrote: > unfortunately the common vfork implementation, which just use > the syscall function to interact with the kernel, does not work > on the cris architecture. The system call vfork is special, on most > architectures just calling syscall is not enough. > The patch below adds the vfork implementation from klibc. > License should be compatible.
this lacks an explanation as to why vfork is so special on cris. different calling convention ? different return values ? something else ? your simple implementation is probably incorrect -- errno cannot be referenced directly. -mike _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
