Em Thu, Jul 09, 2015 at 12:35:03PM +0000, Wang Nan escreveu:
> Hi Arnaldo,
>
> The following changes since commit 3381a29cbec5447086c0f726ee9a88c02e60becc:
>
> bpf tools: Collect map definitions from 'maps' section (2015-07-07 13:41:45
> -0300)
>
> are available in the git repository at:
>
> https://github.com/WangNan0/linux.git perf/ebpf-for-acme
>
> for you to fetch changes up to 072b826c5dc6b2031f4f21c59c57eb6ca1dfa7c0:
So, this is really nice:
38: Test LLVM searching and compiling :ERROR: unable
to find clang.
Hint: Try to install latest clang/llvm to support BPF. Check your $PATH
and 'clang-path' option in [llvm] section of ~/.perfconfig.
LLVM 3.7 or newer is required. Which can be found from http://llvm.org
You may want to try git trunk:
git clone http://llvm.org/git/llvm.git
and
git clone http://llvm.org/git/clang.git
Or fetch the latest clang/llvm 3.7 from pre-built llvm packages for
debian/ubuntu:
http://llvm.org/apt
If you are using old version of clang, change 'clang-bpf-cmd-template'
option in [llvm] section of ~/.perfconfig to:
"$CLANG_EXEC $CLANG_OPTIONS $KERNEL_INC_OPTIONS \
-working-directory $WORKING_DIR -c $CLANG_SOURCE \
-emit-llvm -o - | /path/to/llc -march=bpf -filetype=obj -o -"
(Replace /path/to/llc with path to your llc)
FAILED!
[acme@zoo linux]$
I have the trees cloned and plan to follow these instructions to have this test
passing, to then move on to the next patches, but one request, please change
the above to produce:
38: Test LLVM searching and compiling :(no clang) Ok
run 'perf test -v LLVM' for instructions on having a clang environment
'perf test' will accept either '38' or any substring in the test description and
will run just the ones specified, and with -v we will spare people not
interested
in this eBPF support of these nice verbose instructions :-)
If we find clang but then fail to build, ok, then this is a hard error, I think,
and 'perf test' should FAIL that test.
Regards,
- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
