linux-kernel - Re: [PATCH v4 1/1] perf tools: fix perf build with ARCH=x86

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <593FC733.1080900@mentor.com>
Date:   Tue, 13 Jun 2017 04:06:27 -0700
From:   Jiada Wang <jiada_wang@...tor.com>
To:     Jiri Olsa <jolsa@...hat.com>
CC:     <peterz@...radead.org>, <mingo@...hat.com>, <acme@...nel.org>,
        <alexander.shishkin@...ux.intel.com>, <ak@...ux.intel.com>,
        <sukadev@...ux.vnet.ibm.com>, <wangnan0@...wei.com>,
        <ravi.bangoria@...ux.vnet.ibm.com>, <mhiramat@...nel.org>,
        <jstancek@...hat.com>, <rui.teng@...ux.vnet.ibm.com>,
        <linux-kernel@...r.kernel.org>, <erosca@...adit-jv.com>
Subject: Re: [PATCH v4 1/1] perf tools: fix perf build with ARCH=x86_64

Hello

On 04/10/2017 01:17 AM, Jiri Olsa wrote:
> On Sun, Apr 09, 2017 at 08:02:37PM -0700, jiada_wang@...tor.com wrote:
>> From: Jiada Wang<jiada_wang@...tor.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@...tor.com>
> Acked-by: Jiri Olsa<jolsa@...nel.org>
Is there any other comment on this patch,
How can we get this patch be applied?

> thanks
> jirka