On Wed, 22 Mar 2000, Yoshinobu Inoue wrote: > 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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- 'machine/param.h' required for 'sys/socket.h' Nickolay Dudorov
- Re: 'machine/param.h' required for 'sys/socket.h' Yoshinobu Inoue
- Re: 'machine/param.h' required for 'sys/socket.h... Bruce A. Mah
- Re: 'machine/param.h' required for 'sys/socket.h... Bruce Evans
- Re: 'machine/param.h' required for 'sys/sock... Yoshinobu Inoue
- Re: 'machine/param.h' required for 'sys/... Bruce A. Mah
- Re: 'machine/param.h' required for ... nnd
- Re: 'machine/param.h' required for ... Yoshinobu Inoue
- Re: 'machine/param.h' required ... Bruce Evans
- Re: 'machine/param.h' requi... Yoshinobu Inoue
- Re: 'machine/param.h' requi... Bruce Evans
- Re: 'machine/param.h' requi... Yoshinobu Inoue
- Re: 'machine/param.h' requi... Bruce Evans
- Re: 'machine/param.h' requi... Yoshinobu Inoue