On 28/11/12 09:11, Bruce Evans wrote:
Now the header is non-POSIX, and and also
are documented (in getifaddrs(3)) prerequisites for using it, so the
bug is mostly in the build tool.
Ah. You are right. Sorry for the false alarm.
Martin
___
freebsd-
On 28/11/12 06:21, Martin Sustrik wrote:
On 27/11/12 23:39, Bruce Evans wrote:
#include
INADDR_ANY;
The above results in 'u_int32_t undefined' error, which it shouldn't
according to POSIX.
is careful to only declare uint32_t, but then it is
broken and uses u_int32_t for
On 27/11/12 23:39, Bruce Evans wrote:
#include
INADDR_ANY;
The above results in 'u_int32_t undefined' error, which it shouldn't
according to POSIX.
is careful to only declare uint32_t, but then it is
broken and uses u_int32_t for INADDR_ANY and INADDR_BROADCAST.
u_int32_t is also misused ex
Hi all,
I've just noted the following:
#include
INADDR_ANY;
The above results in 'u_int32_t undefined' error, which it shouldn't
according to POSIX.
I am using FreeBSD 9.0-RELEASE
Martin
___
freebsd-bugs@freebsd.org mailing list
http://lists.free
