Bug#824442: <linux/if.h> and <net/if.h> conflict needs to be resolved
On 2017-02-11 05:44, Niels Thykier wrote:
> On Mon, 16 May 2016 03:12:51 +0100 Ben Hutchings <firstname.lastname@example.org>
> > Source: glibc
> > Version: 2.22-7
> > Severity: serious
> > (Continued from bug #822393.)
> > glibc's <net/if.h> should check whether <linux/if.h> has already been
> > included and, if so, avoid making conflicting definitions.
> > Including the headers in the opposite order works since this change in
> > Linux 4.6:
> > https://git.kernel.org/linus/4a91cb61bb995e5571098188092e296192309c77
> > Ben.
> > --
> > Ben Hutchings
> > 73.46% of all statistics are made up.
> Any news on this bug?
Now that the change have been done on the kernel side, the bug is not
really visible anymore, so nobody really cared about this bug.
I'll see if I can come with a patch in the next days.
Aurelien Jarno GPG: 4096R/1DDD8C9B