From: "leimaohui" <leimaohui@cn.fujitsu.com>
To: Zhenhua Luo <zhenhua.luo@nxp.com>, Andrey Zhizhikin <andrey.z@gmail.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-freescale] Build error of perf
Date: Tue, 8 Sep 2020 03:10:54 +0000 [thread overview]
Message-ID: <73975c970ccf416499ca7d03585f381b@G08CNEXMBPEKD05.g08.fujitsu.local> (raw)
In-Reply-To: <AM6PR0402MB3736C07970A8F6B02F5CDD20EE290@AM6PR0402MB3736.eurprd04.prod.outlook.com>
Hi, Yang
The following is the status of linux-qoriq that I'm using:
-------------------------------------
tmp/work-shared/ubinux-armv8/kernel-source$ git branch
* (HEAD detached at 134788b16485)
Master
-------------------------------------
Best regards
Lei
> -----Original Message-----
> From: Zhenhua Luo <zhenhua.luo@nxp.com>
> Sent: Tuesday, September 8, 2020 10:16 AM
> To: Lei, Maohui <leimaohui@cn.fujitsu.com>; Andrey Zhizhikin
> <andrey.z@gmail.com>
> Cc: meta-freescale@yoctoproject.org
> Subject: RE: [meta-freescale] Build error of perf
>
> Hi Lei,
>
> May I know which branch you are using?
>
>
> Best Regards,
>
> Zhenhua
>
> > -----Original Message-----
> > From: meta-freescale@lists.yoctoproject.org <meta-
> > freescale@lists.yoctoproject.org> On Behalf Of leimaohui via
> > lists.yoctoproject.org
> > Sent: Tuesday, September 8, 2020 10:09 AM
> > To: Andrey Zhizhikin <andrey.z@gmail.com>
> > Cc: meta-freescale@yoctoproject.org
> > Subject: Re: [meta-freescale] Build error of perf
> >
> > Hi, Andrey
> >
> > > I guess you're not building the latest meta-freescale, since the
> > > latest version of kernel recipes (linux-fslc and linux-fslc-imx)
> > > contains version v5.4.62. Or it is possible that you're building
> > > linux-imx kernel, in which case you would have to port the patch on
> > > top of
> > your tree.
> >
> > I'm using linux-qoriq and I have updated to the newest commit of meta-
> > freescale.
> >
> > Best regards
> > Lei
> >
> > > -----Original Message-----
> > > From: Andrey Zhizhikin <andrey.z@gmail.com>
> > > Sent: Monday, September 7, 2020 4:20 PM
> > > To: Lei, Maohui <leimaohui@cn.fujitsu.com>
> > > Cc: meta-freescale@yoctoproject.org
> > > Subject: Re: [meta-freescale] Build error of perf
> > >
> > > Hello Lei,
> > >
> > > On Mon, Sep 7, 2020 at 7:37 AM leimaohui <leimaohui@cn.fujitsu.com>
> > > wrote:
> > > >
> > > > 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
> > > > -u
> > > > bi
> > > > nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-ctl.o:/usr/src/debug/pe
> > > > rf
> > > > /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
> > > > -u
> > > > bi
> > > > nux-linux/perf/1.0-r9/perf-1.0/bench/epoll-wait.o:/usr/src/debug/p
> > > > er
> > > > f/
> > > > 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
> > > -r
> > > 9/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://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2F
> > > > lk
> > > >
> >
> ml.org%2Flkml%2F2020%2F3%2F4%2F313&data=02%7C01%7Czhenhua.
> lu
> > o%40
> > > >
> >
> nxp.com%7C63f43673235e4dd22bc008d8539c24f4%7C686ea1d3bc2b4c6fa9
> 2c
> > d99
> > > >
> >
> c5c301635%7C0%7C0%7C637351277383842133&sdata=Qm7fCOHUJ7J
> O3
> > eb2z%2
> > > > BxQ97ke6sGZJRFhjIJfyuMVtSo%3D&reserved=0
> > >
> > > This is covered by [df35e878d0a51755fb500e2e8e29c7ebb0239756]
> which
> > > is present in the kernel tree and came in with v5.4.56.
> > >
> > > I guess you're not building the latest meta-freescale, since the
> > > latest version of kernel recipes (linux-fslc and linux-fslc-imx)
> > > contains version v5.4.62. Or it is possible that you're building
> > > linux-imx kernel, in which case you would have to port the patch on
> > > top of
> > your tree.
> > >
> > > >
> > > > Best regards
> > > > Lei
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Regards,
> > > Andrey.
> > >
> >
> >
>
>
prev parent reply other threads:[~2020-09-08 3:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-07 5:37 Build error of perf leimaohui
2020-09-07 8:19 ` [meta-freescale] " Andrey Zhizhikin
2020-09-08 2:08 ` leimaohui
2020-09-08 2:16 ` Zhenhua Luo
2020-09-08 3:10 ` leimaohui [this message]
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=73975c970ccf416499ca7d03585f381b@G08CNEXMBPEKD05.g08.fujitsu.local \
--to=leimaohui@cn.fujitsu.com \
--cc=andrey.z@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=zhenhua.luo@nxp.com \
/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).