From owner-freebsd-hackers@FreeBSD.ORG  Thu Jul 10 22:38:10 2003
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0CF6337B401
	for <freebsd-hackers@freebsd.org>;
	Thu, 10 Jul 2003 22:38:10 -0700 (PDT)
Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6A78243F85
	for <freebsd-hackers@freebsd.org>;
	Thu, 10 Jul 2003 22:38:09 -0700 (PDT)
	(envelope-from wes@softweyr.com)
Received: from softweyr.homeunix.net (66-91-236-204.san.rr.com
	[66.91.236.204])	by smtp-relay.omnis.com (Postfix) with ESMTP
	id C50541B319; Thu, 10 Jul 2003 22:38:05 -0700 (PDT)
From: Wes Peters <wes@softweyr.com>
Organization: Softweyr
To: Alin-Adrian Anton <aanton@reversedhell.net>
Date: Thu, 10 Jul 2003 22:38:02 -0700
User-Agent: KMail/1.5.2
References: <0193271C683D5844A478A359271B8F66147AD8@DC1.dynatec.com>
	<20030707164832.L49607@beagle.fokus.fraunhofer.de>
	<3F0790EF.10407@reversedhell.net>
In-Reply-To: <3F0790EF.10407@reversedhell.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200307102238.02405.wes@softweyr.com>
cc: freebsd-hackers@freebsd.org
Subject: Re: raw socket programming SOLVED
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jul 2003 05:38:10 -0000

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