hi romain, On Saturday 23 August 2008 10:12:20 pm Romain Francoise wrote: > That's to be expected. When you use -ansi or -std=c99 GCC doesn't > include the same set of standard headers as when you don't, and as a > result u_int doesn't get defined.
right, and what i was saying is that this is a (fairly minor) bug.
> If you want to compile with -std=c99, use -D_GNU_SOURCE to get the
> full set of headers. See "(libc) Feature Test Macros".
<snip>
> > the strange thing is that with these flags it compiles just fine
> > under freebsd.
>
> Then u_int must be unconditionally available there.
the ifdef surrounding the types in sys/types.h is __USE_BSD, so, i'm not
surprised :)
>
> May I close this bug?
wouldn't it be better to fix libpcap to use standard types? i mean, it's not
like it serves a purpose having it defined as u_int instead of "unsigned
int", nor is it incredibly complicated to fix.
of course if there are other reasons that such flags are necessary to compile
against pcap, for non-trivial reasons, then of course there's an argument for
not changing it but so far i don't see that being the case.
sean
signature.asc
Description: This is a digitally signed message part.
