Re: [configure.ac/uClinux] Adding code for fork/vfork?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Friday, April 15, 2011 18:28:39 Harlan Stenn wrote:
> Giles wrote:
> > Thanks Bob, but some applications don't use conditional compiling and
> > simply use code like this:
> > ============
> > if (uClinux) {
> > 
> > 	*pid = vfork();
> > 
> > } else {
> > 
> > 	*pid = fork();
> > 
> > }
> > ============
> > 
> > Will the cross-compiler go ahead and compile that type of code?
> > Currently, it refuses to proceed because fork() is not available on
> > non-MMU CPU's.
> 
> If you do not want to "force" people to change their code, you will
> probably need to offer a "stub" fork() to link against on non-MMU CPUs.

the majority of the time, it isnt just fork() that needs to change.  any 
exit() in the child needs to be changed to _exit() too.
-mike

Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux