From owner-freebsd-bugs Wed Dec 1 5:40:40 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B9F5414D0F for ; Wed, 1 Dec 1999 05:40:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA01010; Wed, 1 Dec 1999 05:40:03 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Wed, 1 Dec 1999 05:40:03 -0800 (PST) Message-Id: <199912011340.FAA01010@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: i386/15197: Bug in /usr/include/netinet/in.h with u_int32_t Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR i386/15197; it has been noted by GNATS. From: Sheldon Hearn To: eugen@svzserv.kemerovo.su Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: i386/15197: Bug in /usr/include/netinet/in.h with u_int32_t Date: Wed, 01 Dec 1999 14:33:59 +0200 On Wed, 01 Dec 1999 10:28:10 +0700, root@pal.svznov.kemerovo.su wrote: > does not define u_int32_t. It does not include > or something else that defines u_int32_t. Therefore, if a C-program > includes and AFTER, it fails to compile. You're right. That's why you _always_ include before the rest of your headers. This is standard practice. If you find any FreeBSD manual pages in which the SYNOPSIS shows the inclusion of _after_ the inclusion of other headers, please report such documentation bugs in a new PR. You should contact the maintainers of the code that's breaking for you and get them to order their inclusions correctly. I'd close your problem report, but can't access the database at the moment. Hopefully someone else will do the honours. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message