This is the mail archive of the
mailing list for the glibc project.
Re: [PATCH v2] uapi glibc compat: fix compile errors when glibc net/if.h included before linux/if.h
- From: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- To: Mikko Rapeli <mikko dot rapeli at iki dot fi>, "David S. Miller" <davem at davemloft dot net>, Zhang Shengju <zhangshengju at cmss dot chinamobile dot com>, Stephen Hemminger <stephen at networkplumber dot org>, <linux-kernel at vger dot kernel dot org>
- Cc: Jan Engelhardt <jengelh at inai dot de>, Josh Boyer <jwboyer at fedoraproject dot org>, Waldemar Brodkorb <mail at waldemar-brodkorb dot de>, Gabriel Laskar <gabriel at lse dot epita dot fr>, <netfilter-devel at vger dot kernel dot org>, <libc-alpha at sourceware dot org>, Rich Felker <dalias at libc dot org>, nd <nd at arm dot com>
- Date: Mon, 25 Apr 2016 12:26:09 +0100
- Subject: Re: [PATCH v2] uapi glibc compat: fix compile errors when glibc net/if.h included before linux/if.h
- Authentication-results: sourceware.org; auth=none
- Nodisclaimer: True
- References: <1461512707-23058-1-git-send-email-mikko dot rapeli at iki dot fi>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
On 24/04/16 16:45, Mikko Rapeli wrote:
> glibc's net/if.h contains copies of definitions from linux/if.h and these
> conflict and cause build failures if both files are included by application
> source code. Changes in uapi headers, which fixed header file dependencies to
> include linux/if.h when it was needed, e.g. commit 1ffad83d, made the
> net/if.h and linux/if.h incompatibilities visible as build failures for
> userspace applications like iproute2 and xtables-addons.
> This patch fixes compile errors when glibc net/if.h is included before
there should be a way to turn the conflicting definitions
off if a libc header is included first. (the other direction
won't work in general because linux definitions can be wrong
for user space.)
currently the only way to avoid the conflict is to define
__GLIBC__ and a handful of glibc include guard macros that
are not part of any public api, so a libc implementation
might not want to do this.
e.g. the kernel could turn off the potentially conflicting
definitions if the libc defines __LIBC_WANTS_NO_UAPI_DEFS
(it can use finer grain control, but there should be a
non-glibc specific way to do this).