From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
Deng-Cheng Zhu <dengcheng.zhu@gmail.com>,
Ingo Molnar <mingo@redhat.com>, Kyle McMartin <kyle@mcmartin.ca>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Tony Luck <tony.luck@intel.com>,
Will Deacon <will.deacon@arm.com>
Subject: Re: [PATCH] perf tools: fix build for various architectures
Date: Tue, 27 Nov 2012 10:41:16 -0300 [thread overview]
Message-ID: <20121127134116.GC18340@ghostprotocols.net> (raw)
In-Reply-To: <1354018591-26656-1-git-send-email-mark.rutland@arm.com>
Em Tue, Nov 27, 2012 at 12:16:31PM +0000, Mark Rutland escreveu:
> The UAPI changes broke the perf tool, and as of 3.7-rc7, it
> still won't build for arm:
>
> util/../../../arch/arm/include/asm/unistd.h:16:29: fatal error: uapi/asm/unistd.h: No such file or directory
> compilation terminated.
> I've tested this on arm, but I don't have the necessary toolchains to
> check the other cases.
Can you try with my perf/urgent branch?
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux perf/urgent
I tested it with raspbian on a raspberry pi system and also with a cross
compiler on a x86_64 workstation.
I already sent the pull request to Ingo, that should process it and push
to Linus soon.
- Arnaldo
next prev parent reply other threads:[~2012-11-30 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 12:16 [PATCH] perf tools: fix build for various architectures Mark Rutland
2012-11-27 13:41 ` Arnaldo Carvalho de Melo [this message]
2012-11-30 16:40 ` Mark Rutland
2012-11-27 14:12 ` Will Deacon
2012-11-27 14:20 ` Kyle McMartin
2012-11-27 14:41 ` Josh Boyer
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=20121127134116.GC18340@ghostprotocols.net \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=dengcheng.zhu@gmail.com \
--cc=dhowells@redhat.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=schwidefsky@de.ibm.com \
--cc=tony.luck@intel.com \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.