On 02/10/13 17:34, Irek Szczesniak wrote: > Does bash or any other software which does TCP compile in such a > situation? I have the distinct feeling that your build machine, or at > least the layout of your include files, is broken.
Yes, I tested bash compilation and it succeeded to compile. I started the created bash command and run 'cat </dev/tcp/time.nist.gov/13' which gave me: 56567 13-10-02 18:13:07 33 0 0 799.1 UTC(NIST) * I also did a debootstrap [1] of a clean debian testing [2] system and the same layout was found. ksh building would not succeed unless creating the symlink sys -> x86_64-linux-gnu/sys. > Does any *other* Debian machine behave that way? Yes, I tried to compile ksh on Debian 7.0 [3] where there is the same layout of include files, and the compilation failed. After creating the symlink /usr/include/sys -> /usr/include/x86_64-linux-gnu/sys , the compilation succeeded. For instance, on a third debian system I have, on ARM architecture, the sys/socket.h file is found at /usr/include/arm-linux-gnueabihf/sys/socket.h . Giovanni [1] debootsrap is a command that retrieves a clean debian system from the packages repository. The system is installed inside a directory where you can do a chroot to get a clean debian system to work with. [2] Debian testing, which is the system I am working with, is the development version of Debian and will become at some point the new stable version. [3] Debian 7.0 is the current stable version of Debian. -- Giovanni Rapagnani _______________________________________________ ast-developers mailing list [email protected] http://lists.research.att.com/mailman/listinfo/ast-developers
