From owner-freebsd-current  Tue Mar 21  9:48:54 2000
Delivered-To: freebsd-current@freebsd.org
Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36])
	by hub.freebsd.org (Postfix) with ESMTP id 6638637BB85
	for <current@FreeBSD.ORG>; Tue, 21 Mar 2000 09:48:51 -0800 (PST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from m4.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway)
	id CAA18227; Wed, 22 Mar 2000 02:48:14 +0900 (JST)
	(envelope-from shin@nd.net.fujitsu.co.jp)
Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master)
	id CAA05589; Wed, 22 Mar 2000 02:48:14 +0900 (JST)
Received: from localhost ([192.168.245.168]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002)
	id CAA04671; Wed, 22 Mar 2000 02:48:12 +0900 (JST)
To: bde@zeta.org.au
Cc: nnd@mail.nsk.ru, current@FreeBSD.ORG
Subject: Re: 'machine/param.h' required for 'sys/socket.h'
In-Reply-To: <Pine.BSF.4.21.0003220428230.4710-100000@alphplex.bde.org>
References: <20000322013459L.shin@nd.net.fujitsu.co.jp>
	<Pine.BSF.4.21.0003220428230.4710-100000@alphplex.bde.org>
X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN)
X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000322024911Q.shin@nd.net.fujitsu.co.jp>
Date: Wed, 22 Mar 2000 02:49:11 +0900
From: Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>
X-Dispatcher: imput version 990905(IM130)
Lines: 27
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> > I feel requesting inclusion of machine/param.h for any apps
> > which use socket is better. But if there are any other smarter
> > solution, please let me know and I'll appreciate it much.
> 
> <machine/param.h> should never be included by applications since
> it is an implementation detail.
> 
> Specify including <sys/param.h> in apps which use the CMSG*() macros.
> <sys/socket.h> doesn't depend on <*/param.h> unless these macros are used.
> Since these macros are undocumented, applications that use them should
> expect problems :-).
> 
> Bruce

After reading bmah's message, now I am inclined to including
machine/param.h from sys/socket.h for maximum portability, if
there is no spec for it, and if all other platforms doing it.

Of course, I think enough testing for it is necessary.  I can
test make world for it. And if it is OK, then I think it
should be once just committed and checked if any other ports
build problem happens for it, or any other person claim
another problem.

Any more comments for this approach?

Yoshinobu Inoue


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message