From owner-freebsd-questions Wed Oct 14 18:01:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00467 for freebsd-questions-outgoing; Wed, 14 Oct 1998 18:01:02 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from kakapo.pinnacle.co.nz (pinsoft.internet.co.nz [202.37.141.181]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00462 for ; Wed, 14 Oct 1998 18:00:57 -0700 (PDT) (envelope-from jonc@pinnacle.co.nz) Received: from tui.pinnacle.co.nz (tui.pinnacle.co.nz [202.37.163.3]) by kakapo.pinnacle.co.nz (8.8.8/8.8.8) with SMTP id OAA09711; Thu, 15 Oct 1998 14:00:14 +1300 (NZDT) (envelope-from jonc@pinnacle.co.nz) Date: Thu, 15 Oct 1998 14:00:14 +1300 From: Jonathan Chen To: Markus Holmberg cc: Viper , freebsd-questions@FreeBSD.ORG Subject: Re: ip.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 15 Oct 1998, Markus Holmberg wrote: > How do you mean he/I could be missing a #include which defines a > type/structure? Should one need to include files which describe basic > datatypes? Could you please explain, I'm not sure I follow you :) All of these sort of errors mostly boil down to coding errors. Without having a look at the source code you're trying to compile I can't even begin to guess just what's happening. There's nothing wrong with , this is easy to prove: sapphire-/tmp,1:58pm> uname -a FreeBSD sapphire.smp.co.nz 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Thu Oct 15 13:28:36 NZDT 1998 root@sapphire.smp.co.nz:/usr/src/sys/compile/SAPPHIRE i386 sapphire-/tmp,1:58pm> cat a.c #include #include #include #include main () { return 0; } sapphire-/tmp,1:58pm> cc a.c sapphire-/tmp,1:58pm> -- Jonathan Chen | de-moc-ra-cy (di mok' ra see) n. Three wolves | and a sheep voting on what's for dinner. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message