>On Saturday 05 September 2009 16:04:36 Denys Vlasenko wrote: >> +#ifndef O_CLOEXEC >> +# define O_CLOEXEC 0 >> +#endif > >it should be defined by the C library headers. if it isnt, then the port >needs updating and the build should fail. so please drop this cruft.
You probably was thinking about FD_CLOEXEC. :) Yes, FD_CLOEXEC must exist. O_CLOEXEC is a new, Linux specific open() flag. And currently it is not yet defined, since there are many old kernels in the wild which won't understand that. Thus uclibc needs to compile on systems w/o O_CLOEXEC. -- vda _______________________________________________ uClibc mailing list uClibc@uclibc.org http://lists.busybox.net/mailman/listinfo/uclibc
