[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#860013: Bug#824442: <linux/if.h> and <net/if.h> conflict needs to be resolved



On 2017-04-11 03:35, Ben Hutchings wrote:
> Control: tag -1 moreinfo
> 
> On Mon, 10 Apr 2017 10:48:45 +0200 Aurelien Jarno <aurelien@aurel32.net> wrote:
> [...] 
> > Unfortunately I have been pointed on the libc-alpha mailing list that
> > it doesn't work if another file which includes <linux/libc-compat.h>
> > (e.g. <linux/xattr.h>) is included before <net/if.h>. The problem is
> > that the __UAPI_DEF_IF_* constants are set to 1 in <linux/libc-compat.h>
> > even if <linux/if.h> is not included.
> [...]
> 
> Does this affect any real programs, or is this just theoretical (and
> therefore should be downgraded)?

It depends what do you mean by real program. I doubt it still affect
debian packages. The change has been introduced by kernel 4.5, and I
guess by now all the FTBFS have been fixed. At least for stretch, they
might be a few left in sid.

Now some of the fixes might not have reached upstream yet.

If we consider that acceptable, we can lower the severity of the bugs on
both the kernel and the glibc side.

Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net

Attachment: signature.asc
Description: PGP signature


Reply to: