From: Stephen Hemminger <stephen@networkplumber.org>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: Phil Sutter <phil@nwl.cc>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: iproute2 compile and linking errors on Fedora 19
Date: Wed, 1 Nov 2017 07:52:05 +0100 [thread overview]
Message-ID: <20171101075205.398005c3@shemminger-XPS-13-9360> (raw)
In-Reply-To: <CAM_iQpWQ=jXbkFMaG4siav2+nBUSszN_PtYmw9k__TrJLzQtwg@mail.gmail.com>
On Tue, 31 Oct 2017 16:28:20 -0700
Cong Wang <xiyou.wangcong@gmail.com> wrote:
> On Tue, Oct 31, 2017 at 2:10 PM, Stephen Hemminger
> <stephen@networkplumber.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.
next prev parent reply other threads:[~2017-11-01 6:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 17:58 iproute2 compile and linking errors on Fedora 19 Cong Wang
2017-10-31 18:27 ` Cong Wang
2017-10-31 18:59 ` Eric Dumazet
2017-10-31 19:16 ` Roman Mashak
2017-10-31 19:25 ` Eric Dumazet
2017-10-31 21:06 ` Stephen Hemminger
2017-10-31 21:10 ` Stephen Hemminger
2017-10-31 23:28 ` Cong Wang
2017-11-01 6:52 ` Stephen Hemminger [this message]
2018-11-27 0:06 ` Stephen Hemminger
2018-11-27 11:58 ` Phil Sutter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171101075205.398005c3@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.org \
--cc=phil@nwl.cc \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox