From: Josh Boyer <jwboyer@gmail.com>
To: David Howells <dhowells@redhat.com>
Cc: acme@ghostprotocols.net, mingo@kernel.org, tglx@linutronix.de,
bp@alien8.de, namhyung@gmail.com, torvalds@linux-foundation.org,
paulus@samba.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT PULL] UAPI: perf fixes
Date: Tue, 13 Nov 2012 07:51:25 -0500 [thread overview]
Message-ID: <CA+5PVA4jHJeE6nZeZyqHnE9QtMvUGW-xGeKrizwATm96QTxeXQ@mail.gmail.com> (raw)
In-Reply-To: <14097.1352805150@warthog.procyon.org.uk>
On Tue, Nov 13, 2012 at 6:12 AM, David Howells <dhowells@redhat.com> wrote:
> David Howells <dhowells@redhat.com> wrote:
>
>> Josh Boyer <jwboyer@gmail.com> wrote:
>>
>> > This patch seems to break building perf on ppc64. It fails with:
>>
>> Hmmm... Getting my hands on an ARM or ppc/ppc64 box running Fedora is a
>> problem, and as far as I know, this needs to be built natively or maybe
>> cross-compiled with a full environment (including graphics libs).
>
> Actually, having said that, it doesn't need to run Fedora specifically - only
> a sufficiently recent environment that it can build a cutting-edge kernel.
You can just use koji scratch builds if you want to test Fedora kernels
Either arm-koji or ppc-koji should work. If you want actual access to a
machine, I'm sure we can find one.
The error that is hitting ARM and ppc before your patch seemed to also
be hit with sparc and was fixed by David Miller with commit 776260818
by just pointing to "../../arch/sparc/include/uapi/asm/unistd.h". That
might be a temporary solution.
josh
next prev parent reply other threads:[~2012-11-13 12:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 12:51 [GIT PULL] UAPI: perf fixes David Howells
2012-11-12 20:23 ` Josh Boyer
2012-11-13 11:11 ` David Howells
2012-11-13 11:12 ` David Howells
2012-11-13 12:51 ` Josh Boyer [this message]
2012-11-13 15:24 ` David Howells
2012-11-13 15:42 ` Josh Boyer
2012-11-13 15:42 ` Josh Boyer
2012-11-13 16:34 ` Arnaldo Carvalho de Melo
2012-11-15 2:23 ` Xiao Guangrong
2012-11-15 6:17 ` [PATCH 1/2] perf kvm: rename perf_kvm to perf_kvm_stat Xiao Guangrong
2012-11-15 6:17 ` [PATCH 2/2] perf kvm: fix building perf kvm on PowerPC Xiao Guangrong
2012-11-15 10:46 ` David Howells
2012-11-19 8:19 ` Xiao Guangrong
2012-11-19 22:22 ` David Howells
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=CA+5PVA4jHJeE6nZeZyqHnE9QtMvUGW-xGeKrizwATm96QTxeXQ@mail.gmail.com \
--to=jwboyer@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=bp@alien8.de \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).