Re: raw socket programming SOLVED

[ Available lists | Index of freebsd-hackers | Month of Jul 2003 | Week of 10 Jul 2003 | Raw email | View thread | Wrap long lines | Reply | Tag ]
From
Wes Peters <wes@softweyr.com>
Date
10 Jul 2003 22:38:10
Subject
Re: raw socket programming SOLVED
Message-ID
200307102238.02405.wes@softweyr.com

In reply to
Referenced by

[ Hide this part ]
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.

--

Where am I, and what am I doing in this handbasket?

Wes Peters wes@softweyr.com


Elapsed time: 0.153 seconds