linux-kernel - Re: [RFC PATCH v3 28/37] perf tools: Make perf depend on libbpf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150522172419.GG6609@krava.redhat.com>
Date:	Fri, 22 May 2015 19:24:19 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Wang Nan <wangnan0@...wei.com>
Cc:	paulus@...ba.org, a.p.zijlstra@...llo.nl, mingo@...hat.com,
	acme@...nel.org, namhyung@...nel.org, jolsa@...nel.org,
	dsahern@...il.com, ast@...mgrid.com, daniel@...earbox.net,
	brendan.d.gregg@...il.com, masami.hiramatsu.pt@...achi.com,
	lizefan@...wei.com, linux-kernel@...r.kernel.org, pi3orama@....com
Subject: Re: [RFC PATCH v3 28/37] perf tools: Make perf depend on libbpf

On Sun, May 17, 2015 at 10:56:53AM +0000, Wang Nan wrote:

SNIP

>  else
>    TE_PATH=$(TRACE_EVENT_DIR)
>    LIB_PATH=$(LIB_DIR)
> +  BPF_PATH=$(BPF_DIR)
>  endif
>  
>  LIBTRACEEVENT = $(TE_PATH)libtraceevent.a
> @@ -174,6 +177,9 @@ export LIBTRACEEVENT
>  LIBAPI = $(LIB_PATH)libapi.a
>  export LIBAPI
>  
> +LIBBPF = $(BPF_PATH)/libbpf.a
> +export LIBBPF

hum, why does LIBBPF need to be exported?

if it's to match the LIBAPI, it's exported because
of its usage in the util/setup.py, which is not the
case for LIBBPF

jirka
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/