From: "leimaohui" <leimaohui@cn.fujitsu.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Build error of perf
Date: Mon, 7 Sep 2020 05:37:22 +0000 [thread overview]
Message-ID: <ef04e86118784d888616b20806b3d09d@G08CNEXMBPEKD05.g08.fujitsu.local> (raw)
Hi,
By latest meta-freescale, perf build failed, the error is as following:
---------------------------------------------
aarch64-ubinux-linux-ld: /ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `runtime'; /ubinux-dev/build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
aarch64-ubinux-linux-ld: /ubinux-dev/ build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-ctl.c:38: multiple definition of `end'; /ubinux-dev/ /build-ubinux-armv8-multlib-daily/tmp/work/ubinux_armv8-ubinux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/perf/1.0-r9/perf-1.0/tools/perf/bench/epoll-wait.c:93: first defined here
......
---------------------------------------------
It seems that the repository has to merge the following patch:
https://lkml.org/lkml/2020/3/4/313
Best regards
Lei
next reply other threads:[~2020-09-07 5:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 5:37 leimaohui [this message]
2020-09-07 8:19 ` [meta-freescale] Build error of perf Andrey Zhizhikin
2020-09-08 2:08 ` leimaohui
2020-09-08 2:16 ` Zhenhua Luo
2020-09-08 3:10 ` leimaohui
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=ef04e86118784d888616b20806b3d09d@G08CNEXMBPEKD05.g08.fujitsu.local \
--to=leimaohui@cn.fujitsu.com \
--cc=meta-freescale@yoctoproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).