From: Ingo Molnar <mingo@elte.hu>
To: Paul Mackerras <paulus@samba.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf tools: support static build
Date: Mon, 23 Nov 2009 09:45:43 +0100 [thread overview]
Message-ID: <20091123084543.GC23635@elte.hu> (raw)
In-Reply-To: <19209.48577.356560.738625@cargo.ozlabs.ibm.com>
* Paul Mackerras <paulus@samba.org> wrote:
> Michael S. Tsirkin writes:
>
> > Btw, why is it a good idea to force 64/32 bit mode?
> > Why not use the default gcc mode?
>
> On powerpc the gcc default is often 32-bit even when running under a
> 64-bit kernel, but we want to build perf 64-bit if possible.
This can then be forced by doing something like:
make EXTRAFLAGS=-m64
... but i'd not mind a PowerPC default for EXTRAFLAGS either.
Ingo
next prev parent reply other threads:[~2009-11-23 8:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 15:20 [PATCH] perf tools: support static build Michael S. Tsirkin
2009-11-04 11:06 ` Ingo Molnar
2009-11-17 9:23 ` Ingo Molnar
2009-11-22 11:27 ` Michael S. Tsirkin
2009-11-22 11:39 ` Michael S. Tsirkin
2009-11-22 12:02 ` Ingo Molnar
2009-11-22 12:11 ` Michael S. Tsirkin
2009-11-22 13:02 ` Ingo Molnar
2009-11-22 22:40 ` Paul Mackerras
2009-11-23 8:45 ` Ingo Molnar [this message]
2009-11-22 12:06 ` [tip:perf/core] perf tools: Add V=2 option to help debug config issues tip-bot for Michael S. Tsirkin
2009-11-17 9:24 ` [tip:perf/core] perf tools: Support static build tip-bot for Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2009-10-28 7:04 [PATCH] perf tools: support " Michael S. Tsirkin
2009-10-29 8:06 ` Ingo Molnar
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=20091123084543.GC23635@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=paulus@samba.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