From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
jolsa@redhat.com, Namhyung Kim <namhyung@kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Leo Yan <leo.yan@linaro.org>
Subject: Re: tools: Perf: build failed on linux next
Date: Wed, 25 Mar 2020 11:23:23 -0300 [thread overview]
Message-ID: <20200325142323.GE14102@kernel.org> (raw)
In-Reply-To: <CA+G9fYtiroQnpwGu4oLA=ChmS==XGpmAAqB_Oa9nrXC3vQ0xsQ@mail.gmail.com>
Em Wed, Mar 25, 2020 at 07:37:10PM +0530, Naresh Kamboju escreveu:
> Perf build broken on Linux next and mainline on x86_64.
>
> find: unknown predicate `-m64/arch'
> Try 'find --help' for more information.
> HOSTCC /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/pmu-events/json.o
> LD /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/libperf-in.o
> x86_64-linaro-linux-gcc: warning: '-x c' after last input file has no effect
> GEN perf-archive
> AR /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/libperf.a
> GEN perf-with-kcore
> x86_64-linaro-linux-gcc: error: unrecognized command line option
> '-m64/include/uapi/asm-generic/errno.h'
> x86_64-linaro-linux-gcc: fatal error: no input files
> compilation terminated.
> HOSTCC /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/pmu-events/jevents.o
> MKDIR /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/pmu-events/
> x86_64-linaro-linux-gcc: warning: '-x c' after last input file has no effect
> HOSTCC /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/pmu-events/jsmn.o
> x86_64-linaro-linux-gcc: error: unrecognized command line option
Right, there is some patch handling this, which we're trying to process
but has some issues.
- Arnaldo
> '-m64/include/uapi/asm-generic/errno.h'
> x86_64-linaro-linux-gcc: fatal error: no input files
> compilation terminated.
> make[3]: Nothing to be done for
> '/srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/plugins/libtraceevent-dynamic-list'.
> GEN /srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/python/perf.so
> Traceback (most recent call last):
> File "util/setup.py", line 6, in <module>
> cc_is_clang = b"clang version" in Popen([cc, "-v"],
> stderr=PIPE).stderr.readline()
> File "/srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/recipe-sysroot-native/usr/lib/python2.7/subprocess.py",
> line 394, in __init__
> errread, errwrite)
> File "/srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/recipe-sysroot-native/usr/lib/python2.7/subprocess.py",
> line 1047, in _execute_child
> raise child_exception
> OSError: [Errno 2] No such file or directory
> cp: cannot stat
> '/srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/python_ext_build/lib/perf*.so':
> No such file or directory
> Makefile.perf:590: recipe for target
> '/srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/python/perf.so'
> failed
> make[2]: *** [/srv/oe/build/tmp-lkft-glibc/work/intel_corei7_64-linaro-linux/perf/1.0-r9/perf-1.0/python/perf.so]
> Error 1
> make[2]: *** Waiting for unfinished jobs....
>
> ref:
> https://ci.linaro.org/view/lkft/job/openembedded-lkft-linux-next/DISTRO=lkft,MACHINE=intel-corei7-64,label=docker-lkft/733/consoleText
>
> --
> Linaro LKFT
> https://lkft.linaro.org
--
- Arnaldo
next prev parent reply other threads:[~2020-03-25 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-25 14:07 tools: Perf: build failed on linux next Naresh Kamboju
2020-03-25 14:23 ` Arnaldo Carvalho de Melo [this message]
2020-03-25 14:55 ` Naresh Kamboju
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=20200325142323.GE14102@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@redhat.com \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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