From: Jiada Wang <jiada_wang@mentor.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<wangnan0@huawei.com>, <ravi.bangoria@linux.vnet.ibm.com>,
<mhiramat@kernel.org>, <linux-kernel@vger.kernel.org>,
<erosca@de.adit-jv.com>
Subject: Re: [PATCH v3 1/1] perf tools: fix perf build with ARCH=x86_64
Date: Sun, 9 Apr 2017 19:43:15 -0700 [thread overview]
Message-ID: <58EAF143.7090509@mentor.com> (raw)
In-Reply-To: <20170409172711.GA16588@krava>
Hello Jiri
On 04/09/2017 10:27 AM, Jiri Olsa wrote:
> On Tue, Apr 04, 2017 at 11:25:44PM -0700, jiada_wang@mentor.com wrote:
>> From: Jiada Wang<jiada_wang@mentor.com>
>>
>> with commit: 0a943cb10ce78 (tools build: Add HOSTARCH Makefile variable)
>> the following build failure is seen when build with ARCH=x86_64
> is that described somewhere as a valid building interface?
> I never use it so I have no idea.. would you describe your
> build env/process?
I used "ARCH=x86_64 make -C tools perf V=1" to build perf for x86_64 ARCH.
>> In file included from util/event.c:2:0:
>> tools/include/uapi/linux/mman.h:4:27: fatal error: uapi/asm/mman.h: No such file or directory
>> compilation terminated.
>>
>> fix this issue by use SRCARCH instead of ARCH in perf.
> please describe also the the issue itself in the changelog, not just the fix
I will update changelog with detail information about the issue in v4
>
>
> so objtool is using SRCARCH this way, I guess it's fine
>
> if we go this way, you also need to change the pmu-events/Build
> and there's some comment using $(ARCH) in util/header.c
will update pmu-events/Build in v4
> thanks,
> jirka
Thanks,
Jiada
next prev parent reply other threads:[~2017-04-10 2:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 6:25 [PATCH v3 0/1] fix perf build issue when ARCH=x86_64 jiada_wang
2017-04-05 6:25 ` [PATCH v3 1/1] perf tools: fix perf build with ARCH=x86_64 jiada_wang
2017-04-09 17:27 ` Jiri Olsa
2017-04-10 2:43 ` Jiada Wang [this message]
2017-04-10 7:44 ` Jiri Olsa
2017-04-17 9:31 ` Jiada Wang
2017-04-17 18:30 ` Jiri Olsa
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=58EAF143.7090509@mentor.com \
--to=jiada_wang@mentor.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=erosca@de.adit-jv.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@linux.vnet.ibm.com \
--cc=wangnan0@huawei.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