On Sunday 18 April 2010 05:28:06 Nguyen Thai Ngoc Duy wrote: > On Sun, Apr 18, 2010 at 8:27 AM, Rob Landley <[email protected]> wrote: > > On Thursday 15 April 2010 14:58:26 Nguyễn Thái Ngọc Duy wrote: > >> These empty headers are to prevent #include errors. Of course > >> those #include may be wrapped inside #ifdefs and excluded, but that > >> would turn libbb.h into a #ifdef mess. > >> > >> Note that all missing declaration is in mingw.h, not in these files. > >> > >> Signed-off-by: Nguyễn Thái Ngọc Duy <[email protected]> > >> --- > >> 0 files changed, 0 insertions(+), 0 deletions(-) > >> create mode 100644 win32/grp.h > >> create mode 100644 win32/netdb.h > >> create mode 100644 win32/pwd.h > >> create mode 100644 win32/sys/ioctl.h > >> create mode 100644 win32/sys/mman.h > >> create mode 100644 win32/sys/poll.h > >> create mode 100644 win32/sys/socket.h > >> create mode 100644 win32/sys/wait.h > >> create mode 100644 win32/termios.h > > > > Surely this is a defect in your build environment? These are standard > > system headers. Your C library is defective. > > Welcome to Windows.
How is a clearly defective build environment busybox's problem? If mingw doesn't work, either fix it or try cygwin. Both as open source build environments, and for all I know there's more. (I don't do windows, but wasn't djgpp a build environment at one point?) If somebody came to the busybox list and went "I want to build against newlib+libgloss, but my build environment hasn't got these headers, I need you to add them to the busybox source for me", there's no way we'd do that. Your position is that Windows is different? Special? Rob -- Latency is more important than throughput. It's that simple. - Linus Torvalds _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
