bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: bpf <bpf@vger.kernel.org>
Subject: finding libelf
Date: Tue, 2 Feb 2021 19:50:23 -0800	[thread overview]
Message-ID: <8a6894e9-71ef-09e3-64fa-bf6794fc6660@infradead.org> (raw)

Hi,

I see this sometimes when building a kernel: (on x86_64,
with today's linux-next 20210202):


CONFIG_CGROUP_BPF=y
CONFIG_BPF=y
CONFIG_BPF_SYSCALL=y
CONFIG_ARCH_WANT_DEFAULT_BPF_JIT=y
CONFIG_BPF_PRELOAD=y
CONFIG_BPF_PRELOAD_UMD=m
CONFIG_HAVE_EBPF_JIT=y


Auto-detecting system features:
...                        libelf: [ ^[[31mOFF^[[m ]
...                          zlib: [ ^[[31mOFF^[[m ]
...                           bpf: [ ^[[31mOFF^[[m ]

No libelf found
make[5]: [Makefile:287: elfdep] Error 1 (ignored)
No zlib found
make[5]: [Makefile:290: zdep] Error 1 (ignored)
BPF API too old
make[5]: [Makefile:293: bpfdep] Error 1 (ignored)


but pkg-config tells me:

$ pkg-config --modversion  libelf
0.168
$ pkg-config --libs  libelf
-lelf


Any ideas?

thanks.

-- 
~Randy


             reply	other threads:[~2021-02-03  3:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03  3:50 Randy Dunlap [this message]
2021-02-03 10:57 ` finding libelf Toke Høiland-Jørgensen
2021-02-03 17:20   ` Randy Dunlap
2021-02-03 19:39     ` Andrii Nakryiko
2021-02-03 20:06       ` Andrii Nakryiko
2021-02-03 20:33         ` Jiri Olsa
2021-02-04 10:55         ` Jiri Olsa
2021-02-03 20:09       ` Randy Dunlap
2021-02-03 20:12         ` Andrii Nakryiko
2021-02-03 20:14           ` Randy Dunlap
2021-02-03 20:33             ` Andrii Nakryiko
2021-02-03 20:36               ` Randy Dunlap
2021-02-03 20:41                 ` Randy Dunlap
2021-02-03 20:41                 ` Andrii Nakryiko
2021-02-03 20:57                   ` Randy Dunlap
2021-02-03 21:31                     ` Andrii Nakryiko

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=8a6894e9-71ef-09e3-64fa-bf6794fc6660@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=bpf@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).