linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leo Yan <leo.yan@linaro.org>
To: Thomas Backlund <tmb@mageia.org>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Mike Leach <mike.leach@linaro.org>,
	Suzuki Kuruppassery Poulose <suzuki.poulose@arm.com>
Subject: Re: perf build error with gcc 10 on arm and aarch64
Date: Tue, 5 May 2020 21:38:28 +0800	[thread overview]
Message-ID: <20200505133828.GC17996@leoy-ThinkPad-X240s> (raw)
In-Reply-To: <ed17a79e-81cd-8514-aaa7-13223bd1c789@mageia.org>

On Tue, May 05, 2020 at 04:11:14PM +0300, Thomas Backlund wrote:
> Den 05-05-2020 kl. 07:10, skrev Leo Yan:
> > 
> > Hi Thomas,
> > 
> > [ + Mathieu/Mike/Suzuki ]
> > 
> > On Mon, May 04, 2020 at 10:22:27PM +0300, Thomas Backlund wrote:
> > > This is building perf from kernel-5.6.10 on armv7hl and aarch64:
> > > 
> > > Compiler is gcc 10.1.0-RC
> > > 
> > > 
> > >    LD       perf-in.o
> > > ld: arch/perf-in.o: in function `.LANCHOR0':
> > > /home/iurt/rpmbuild/BUILD/kernel-arm/linux-5.6/tools/perf/util/include/../../util/cs-etm.h:118:
> > > multiple definition of `traceid_list'; util/perf-in.o:/home/iurt/rpmbuild/BUILD/kernel-arm/linux-5.6/tools/perf/util/cs-etm.h:118:
> > > first defined here
> > > make[3]: *** [/home/iurt/rpmbuild/BUILD/kernel-arm/linux-5.6/tools/build/Makefile.build:145:
> > > perf-in.o] Error 1
> > > 
> > >    LD       perf-in.o
> > > ld: arch/perf-in.o:/home/iurt/rpmbuild/BUILD/kernel-aarch64/linux-5.6/tools/perf/util/include/../../util/cs-etm.h:118:
> > > multiple definition of `traceid_list'; util/perf-in.o:/home/iurt/rpmbuild/BUILD/kernel-aarch64/linux-5.6/tools/perf/util/cs-etm.h:118:
> > > first defined here
> > > make[3]: *** [/home/iurt/rpmbuild/BUILD/kernel-aarch64/linux-5.6/tools/build/Makefile.build:145:
> > > perf-in.o] Error 1
> > > make[2]: *** [Makefile.perf:616: perf-in.o] Error 2
> > > make[1]: *** [Makefile.perf:225: sub-make] Error 2
> > > make: *** [Makefile:70: all] Error 2
> > > 
> > > 
> > > The same build succeeds with gcc 9.3.0
> > 
> > Thanks for reporting the issue.
> > 
> > Could you help confirm if below change can resolve this issue?
> 
> Yes,
> 
> fix confirmed on i586, x86_64, armv7hl and aarch64 builds
> 
> so I guess you can add:
> 
> Reported-by: Thomas Backlund <tmb@mageia.org>
> Tested-by: Thomas Backlund <tmb@mageia.org>

Thanks, Thomas!  Have sent formal patch with your and Mike's tags.

Leo

      reply	other threads:[~2020-05-05 13:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 19:22 perf build error with gcc 10 on arm and aarch64 Thomas Backlund
     [not found] ` <EqtrWAkr-uZW90nfEH5i3KgHuQU8DLdDEXPSqRws1z9zrOixq2T0wt5uDhcFI5JVaIr_DGq7PP9Z-Q3B-LAaqQ==@protonmail.internalid>
2020-05-05  4:10 ` Leo Yan
2020-05-05 10:26   ` Mike Leach
2020-05-05 10:47     ` Leo Yan
2020-05-05 13:11   ` Thomas Backlund
2020-05-05 13:38     ` Leo Yan [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=20200505133828.GC17996@leoy-ThinkPad-X240s \
    --to=leo.yan@linaro.org \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mike.leach@linaro.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=suzuki.poulose@arm.com \
    --cc=tmb@mageia.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).