OK, but what to do about already existing code ....
Fix the usage of it :-)
I don't dare to, as I don't see a commonly agreed strategy. _I_ would
just replace the code mentioned by p = vfork(); but I feel that we would
get bashed (and no pushing upstream) for this as traditionally everybody
is used to do fork() and vfork() seems to be lead some kind of secret life.
Maybe a strategy might be to completely get rid of vfork() and do a
compiler define vfork -> fork in some top level make file but this asks
for really nasty problems in those (many more than no) cases when the
"easy porting" does not hold. (E.g. I just started using the boa version
0.94 instead of 0.93 and there seems to be a small vfork glitch: it does
not return to the command line when started without the -d option. I did
report this to the boa team.)
IIRC the uClinux-dist adds the __uClinux__ for !MMU builds, so even if the
toolchain doesn't define it you are ok.
I'm positive that there will be a solution :). The name __uClinux__ just
seems not very right.
-Michael
_______________________________________________
uClinux-dev mailing list
uClinux-dev@uclinux.org
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by uclinux-dev@uclinux.org
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev
