From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] perf build questions
Date: Tue, 06 Oct 2009 20:02:48 +0200 [thread overview]
Message-ID: <1254852168.17055.1.camel@laptop> (raw)
In-Reply-To: <20091006102626.8b4f7810.randy.dunlap@oracle.com>
On Tue, 2009-10-06 at 10:26 -0700, Randy Dunlap wrote:
> On Tue, 06 Oct 2009 10:48:59 +0200 Peter Zijlstra wrote:
>
> > On Mon, 2009-10-05 at 13:17 -0700, Randy Dunlap wrote:
> > > Hi,
> > >
> > > How do I build 'perf' for an i386 target when running on x86_64?
> >
> > make NO_64BIT=1
>
> $ make NO_64BIT=1 all
> $ file perf
> perf: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), for GNU/Linux 2.6.4, dynamically linked (uses shared libs), not stripped
>
>
> Shouldn't that be a 32-bit executable for i386?
> Am I confused? (you don't have to answer that)
# uname -a
Linux twins 2.6.31-tip #212 SMP PREEMPT Tue Sep 22 12:02:22 CEST 2009
x86_64 GNU/Linux
# rm perf
# make NO_64BIT=1 perf
# file perf
perf: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not
stripped
seems to work for me...
next prev parent reply other threads:[~2009-10-06 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 20:17 [patch] perf build questions Randy Dunlap
2009-10-05 20:47 ` Frederic Weisbecker
2009-10-06 8:48 ` Peter Zijlstra
2009-10-06 17:26 ` Randy Dunlap
2009-10-06 18:02 ` Peter Zijlstra [this message]
2009-10-06 18:05 ` Kyle McMartin
2009-10-06 18:09 ` Randy Dunlap
2009-10-12 8:47 ` Ingo Molnar
2009-10-12 15:34 ` Randy Dunlap
2009-10-12 6:35 ` Ingo Molnar
2009-10-12 15:33 ` Randy Dunlap
2009-10-12 6:52 ` [tip:perf/urgent] perf tools: Fix const char type propagation tip-bot for Randy Dunlap
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=1254852168.17055.1.camel@laptop \
--to=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=randy.dunlap@oracle.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