raw socket programming SOLVED
Alin-Adrian Anton
aanton at reversedhell.net
Fri Jul 11 06:33:34 PDT 2003
Wes Peters wrote:
>On Saturday 05 July 2003 08:01 pm, Alin-Adrian Anton wrote:
>
>
>>Yes, it works now, with these includes:
>>-------------------------------
>>#include <sys/types.h>
>>#include <sys/socket.h>
>>#include <stdio.h>
>>#include <string.h>
>>#include <errno.h>
>>
>>#include <netinet/in_systm.h>
>>#include <netinet/in.h>
>>#include <netinet/ip.h>
>>
>>#include <unistd.h>
>>#include <netinet/tcp.h>
>>-------------------------------
>>
>>
>
>Believe it or not, the advice in style(9) is quite helpful in putting
>include files in their correct order. I'm so used to doing things in
>similar order that I re-wrote your original program as:
>
>#include <sys/types.h>
>#include <sys/socket.h>
>
>#include <netinet/in_systm.h>
>#include <netinet/in.h>
>#include <netinet/ip.h>
>#include <netinet/tcp.h>
>
>#include <errno.h>
>#include <stdio.h>
>#include <string.h>
>#include <unistd.h>
>
>int main() { printf("foo\n"); }
>
>after grepping for n_long in /usr/include. The order of the netinet
>includes; in.h then ip.h then tcp.h, seems logical to me. Perhaps a
>(re-) reading of the instructions on include files in style(9) is in
>order.
>
>
>
Thank you, I just read it. You are right. :-)
Alin.
More information about the freebsd-hackers
mailing list