public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: jiada_wang@mentor.com
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	alexander.shishkin@linux.intel.com, ak@linux.intel.com,
	sukadev@linux.vnet.ibm.com, wangnan0@huawei.com,
	ravi.bangoria@linux.vnet.ibm.com, mhiramat@kernel.org,
	jstancek@redhat.com, rui.teng@linux.vnet.ibm.com,
	linux-kernel@vger.kernel.org, erosca@de.adit-jv.com
Subject: Re: [PATCH v4 1/1] perf tools: fix perf build with ARCH=x86_64
Date: Mon, 10 Apr 2017 10:17:15 +0200	[thread overview]
Message-ID: <20170410081715.GC25354@krava> (raw)
In-Reply-To: <1491793357-14977-2-git-send-email-jiada_wang@mentor.com>

On Sun, Apr 09, 2017 at 08:02:37PM -0700, jiada_wang@mentor.com wrote:
> From: Jiada Wang <jiada_wang@mentor.com>
> 
> with commit: 0a943cb10ce78 (tools build: Add HOSTARCH Makefile variable)
> when build for ARCH=x86_64, ARCH=x86_64 is passed to perf instead of
> ARCH=x86, so perf package searchs header files from
> tools/arch/x86_64/include, which doesn't exist.
> 
> the following build failure is seen when build with ARCH=x86_64
> 
> 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.
> 
> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>

Acked-by: Jiri Olsa <jolsa@kernel.org>

thanks
jirka

  reply	other threads:[~2017-04-10  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10  3:02 [PATCH v4 0/1] fix perf build issue when ARCH=x86_64 jiada_wang
2017-04-10  3:02 ` [PATCH v4 1/1] perf tools: fix perf build with ARCH=x86_64 jiada_wang
2017-04-10  8:17   ` Jiri Olsa [this message]
2017-06-13 11:06     ` Jiada Wang
2017-06-16 19:38   ` [tip:perf/urgent] perf tools: Fix " tip-bot for Jiada Wang

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=20170410081715.GC25354@krava \
    --to=jolsa@redhat.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=erosca@de.adit-jv.com \
    --cc=jiada_wang@mentor.com \
    --cc=jstancek@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=rui.teng@linux.vnet.ibm.com \
    --cc=sukadev@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