From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============4707123312745432704==" MIME-Version: 1.0 From: Richard Henderson To: elfutils-devel@lists.fedorahosted.org Subject: Re: [PATCH] Fix BPF check for kernels < 3.20 Date: Tue, 06 Sep 2016 10:00:42 -0700 Message-ID: In-Reply-To: 1473067277.27552.130.camel@redhat.com --===============4707123312745432704== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 09/05/2016 02:21 AM, Mark Wielaard wrote: > On Wed, 2016-08-31 at 16:21 +0200, Mark Wielaard wrote: >> > Thanks, that does look like the correct configure check. >> > >> > But it seems that BPF_PSEUDO_MAP_FD is the only missing constant >> > introduced since 3.18 (when linux/bpf.h was added) that we use. >> > So maybe we could simply define it ourselves when not found. So we can >> > build against any linux/bpf.h out there. >> > >> > What do people think of the following? > I tested it against the latest stable kernel and headers from the 3.18 > kernel and it seems to work fine. Any objections to commit the attached? None. r~ --===============4707123312745432704==--