I think you'll find that most of linux/... is the kernel half of the
libc headers; I recall that they get included by bits/... who get
included by net/... and netinet/.. and sys/... and it's all a hideous
mess of preprocessor directives; you're supposed to use the posix
header and pretend the linux/... headers don't exist.  But obviously
that doesn't work for your case :(

2009/1/2 Peter Miller <pmil...@opensource.org.au>:
> On Fri, 2009-01-02 at 21:05 +1100, Peter Miller wrote:
>> I think I'll have a look at how strace solved this.
>
> Urrgh.  barf.   They don't compile them, they preprocess them into an
> include file, dodging all the ugly bits.  At no time do they all get
> included into the same compilation unit.
>
>
> Also, having (hackishly) gotten past the <net/if.h> vs <linux/if.h>
> problem, it turns out that <netinet/in.h> vs <linux/in.h> has exactly
> the same problem.  But the same ugly hack doesn't work.   :-(
>
>
> --
> Regards
> Peter Miller <pmil...@opensource.org.au>
> /\/\*        http://www.canb.auug.org.au/~millerp/
>
> PGP public key ID: 1024D/D0EDB64D
> fingerprint = AD0A C5DF C426 4F03 5D53  2BDB 18D8 A4E2 D0ED B64D
> See http://www.keyserver.net or any PGP keyserver for public key.
> _______________________________________________
> coders mailing list
> coders@slug.org.au
> http://lists.slug.org.au/listinfo/coders
>
_______________________________________________
coders mailing list
coders@slug.org.au
http://lists.slug.org.au/listinfo/coders

Reply via email to