[uClibc]Re: vfork test fail in ppc target
Miles Bader
miles at lsi.nec.co.jp
Wed Sep 4 09:46:24 UTC 2002
Colin.Helliwell at Zarlink.Com writes:
> As regards addressing this issue, I guess there's a number of options:
> - If its a kernel bug, either fix it (?) or "un-implement" the vfork
> syscall so that the uclibc vfork falls back on fork as it is already
> designed to do.
> - Change the uClibc vfork() to only use the fork system call (ie as glibc
> does)
> - Force a "#define vfork fork" in the uClibc files that use it, such as
> system.c and popen.c
I'm confused by why you're suggesting all of the above.
vfork and fork are _different_, and applications have to be aware of the
differences. Do you have an application [not a test program] that's
using vfork, and failing?
If so, perhaps the application is simply wrong, and should be change to
either use `fork', or to just not do stuff that runs afoul of vfork.
-Miles
--
80% of success is just showing up. --Woody Allen
More information about the uClibc
mailing list