From: Sudeep Holla <sudeep.holla@arm.com>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Wang Nan <wangnan0@huawei.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
acme@kernel.org
Subject: Re: [PATCH 2/2] tools: perf: fix build error in uapi/linux/mman.h
Date: Tue, 10 Jan 2017 17:13:34 +0000 [thread overview]
Message-ID: <eb503909-e630-5d5a-4cb8-0ecc43d8fa54@arm.com> (raw)
In-Reply-To: <20170110144348.GA2176@redhat.com>
On 10/01/17 14:43, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jan 10, 2017 at 10:22:50AM +0000, Sudeep Holla escreveu:
>> All the other occurrence refer "uapi/asm-generic/*.h" directly instead
>> of "uapi/asm/*.h" in tools/include except mman.h. Without this patch,
>> the following build failure is seen.
>>
>
> Seen where? I don't see it here, and I build perf for lots of different
> systems:
>
[...]
> The ones for cross compiling (-x-) mostly don't have the full set of
> devel packages, but even so, I am not seeing this problem, can you
> please describe more precisely the environment where you notice this
> problem?
>
> Assuming this is on ARM, based on your e-mail address, for instance,
> debian:experimental-x-arm64 is built with this Dockerfile, look at the
> packages used:
In fact this is on x86_64. I noticed the actual difference today when I
was experimenting further.
make ARCH=x86_64 -C tools O=/tmp/perf perf ----> fails to build
make -C tools O=/tmp/perf perf ----> Builds fine
--
Regards,
Sudeep
prev parent reply other threads:[~2017-01-10 17:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 10:22 [PATCH 1/2] tools: perf: fix linker error when libelf config is disabled Sudeep Holla
2017-01-10 10:22 ` [PATCH 2/2] tools: perf: fix build error in uapi/linux/mman.h Sudeep Holla
2017-01-10 14:43 ` Arnaldo Carvalho de Melo
2017-01-10 17:13 ` Sudeep Holla [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=eb503909-e630-5d5a-4cb8-0ecc43d8fa54@arm.com \
--to=sudeep.holla@arm.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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
Powered by JetHome