[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171101075205.398005c3@shemminger-XPS-13-9360>
Date: Wed, 1 Nov 2017 07:52:05 +0100
From: Stephen Hemminger <stephen@...workplumber.org>
To: Cong Wang <xiyou.wangcong@...il.com>
Cc: Phil Sutter <phil@....cc>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: iproute2 compile and linking errors on Fedora 19
On Tue, 31 Oct 2017 16:28:20 -0700
Cong Wang <xiyou.wangcong@...il.com> wrote:
> On Tue, Oct 31, 2017 at 2:10 PM, Stephen Hemminger
> <stephen@...workplumber.org> wrote:
> >
> > IPPROTO_MH comes from include/uapi/linux/in6.h
> > Maybe it is trying to use old kernel headers from libc.
>
> So newer iproute2 is not supposed to work with older
> kernel header??
Iproute2 has always supplied it's own sanitized kernel headers.
This allows it to be built on older systems where newer definitions in kernel
headers are missing. If you point the kernel header for either kernel package
or glibc, it can't build.
This was done to avoid having to have source full of #ifdef XXX.
Kernel user API is stable enough that newer versions of iproute2 fine.
If a new feature is requested on old kernel it is reported as an error or ignored.
Powered by blists - more mailing lists