All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose R R <jose.r.r@metztli.com>
To: linux-kernel@vger.kernel.org
Cc: Debian kernel maintainers <debian-kernel@lists.debian.org>
Subject: "BPF API too old" with linux-tools 4.12.9
Date: Mon, 28 Aug 2017 07:24:40 -0700	[thread overview]
Message-ID: <CAM12Q5Ri2_P76A6xSL9VApf+qSLQfJ-Ofb7ZcjssXsebzxj5VQ@mail.gmail.com> (raw)

Any help would appreciated as linux-headers common are not built in
reiser4 custom kernel build:

make[7]: Leaving directory '/usr/src/build/kernel/build/linux/tools/build'
/usr/bin/make FIXDEP=1 -f Makefile.perf
make[7]: Entering directory '/usr/src/build/kernel/build/linux/tools/perf'

Auto-detecting system features:
...                         dwarf: [ ^[[32mon^[[m  ]
...            dwarf_getlocations: [ ^[[32mon^[[m  ]
...                         glibc: [ ^[[32mon^[[m  ]
...                          gtk2: [ ^[[32mon^[[m  ]
...                      libaudit: [ ^[[32mon^[[m  ]
...                        libbfd: [ ^[[31mOFF^[[m ]
...                        libelf: [ ^[[32mon^[[m  ]
...                       libnuma: [ ^[[32mon^[[m  ]
...        numa_num_possible_cpus: [ ^[[32mon^[[m  ]
...                       libperl: [ ^[[32mon^[[m  ]
...                     libpython: [ ^[[32mon^[[m  ]
...                      libslang: [ ^[[32mon^[[m  ]
...                     libcrypto: [ ^[[32mon^[[m  ]
...                     libunwind: [ ^[[32mon^[[m  ]
...            libdw-dwarf-unwind: [ ^[[32mon^[[m  ]
...                          zlib: [ ^[[32mon^[[m  ]
...                          lzma: [ ^[[32mon^[[m  ]
...                     get_cpuid: [ ^[[32mon^[[m  ]
...                           bpf: [ ^[[31mOFF^[[m ]

Makefile.config:456: BPF API too old. Please install recent kernel
headers. BPF support in 'perf record' is disabled.


Best Professional Regards.

                 reply	other threads:[~2017-08-28 14:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAM12Q5Ri2_P76A6xSL9VApf+qSLQfJ-Ofb7ZcjssXsebzxj5VQ@mail.gmail.com \
    --to=jose.r.r@metztli.com \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.