On Wed, 11 Dec 2002, Mike Barcroft wrote:
Nate Lawson [EMAIL PROTECTED] writes:
What's the proper way to get a typedef for u_int? Is there a doc
somewhere on what we expect in terms of #defines for 3rd party application
authors?
sys/types.h will give you a typedef, provided you aren't
Hmm, which of these defines claims posix src? -D_ANSI_SOURCE ?
cc -O -c -O -pipe -mcpu=pentiumpro -mcpu=pentiumpro -I./../include
[...]
u_int is undocumented and unportable, so it probably shouldn't be
used. It's only 3 characters shorter than `unsigned' anyway.
It's for ports.
And this
Nate Lawson [EMAIL PROTECTED] writes:
On Wed, 11 Dec 2002, Mike Barcroft wrote:
Nate Lawson [EMAIL PROTECTED] writes:
What's the proper way to get a typedef for u_int? Is there a doc
somewhere on what we expect in terms of #defines for 3rd party application
authors?
sys/types.h
Mike Barcroft [EMAIL PROTECTED] writes:
Nate Lawson [EMAIL PROTECTED] writes:
cc -O -c -O -pipe -mcpu=pentiumpro -mcpu=pentiumpro -I./../include
-I./.. -DDIRENT=1 -DDIRENT=1 -DSTDC_HEADERS=1 -DHAVE_UNISTD_H=1
-DHAVE_FCNTL_H=1 -DHAVE_ST_RDEV=1 -DHAVE_TM_ZONE=1
-DHAVE_LONG_FILE_NAMES=1
On Fri, Dec 13, 2002 at 11:48:23PM +0100, Marc Recht wrote:
Hmm, which of these defines claims posix src? -D_ANSI_SOURCE ?
cc -O -c -O -pipe -mcpu=pentiumpro -mcpu=pentiumpro -I./../include
[...]
u_int is undocumented and unportable, so it probably shouldn't be
used. It's only 3
On Fri, 13 Dec 2002, Mike Barcroft wrote:
I fixed a port like this recently. _ANSI_SOURCE was actually added by
the port, not the application vendor, in that case.
Wait a minute, I think this might be the same port. Is it gnu-finger?
If so, try the attached patch. Kris was going to
Nate Lawson [EMAIL PROTECTED] writes:
What's the proper way to get a typedef for u_int? Is there a doc
somewhere on what we expect in terms of #defines for 3rd party application
authors?
sys/types.h will give you a typedef, provided you aren't writing a
POSIX or X/Open application. If you're
