From: Randy Dunlap <randy.dunlap@oracle.com>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
lkml <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [patch] perf build questions
Date: Tue, 6 Oct 2009 11:09:41 -0700 [thread overview]
Message-ID: <20091006110941.eebe58af.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091006180551.GB11702@bombadil.infradead.org>
On Tue, 6 Oct 2009 14:05:51 -0400 Kyle McMartin wrote:
> On Tue, Oct 06, 2009 at 10:26:26AM -0700, Randy Dunlap wrote:
> > $ 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)
> >
>
> Are you running a 32-bit userspace, with x86_64 kernel? Or running
> x86_64 userspace as well and trying to crossbuild for i386? In the
> latter case NO_64BIT won't do what you hope, it's to avoid trying to
> build a 64-bit binary in the former case.
All 64-bit userspace & kernel. so that fails. Thanks.
> You could force -m32 into CFLAGS in the second case, but unless you have
> the proper i386 bi-arch toolchain installed (glibc, etc.) it likely
> won't build...
I'll test/check etc.
---
~Randy
next prev parent reply other threads:[~2009-10-06 18:18 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
2009-10-06 18:05 ` Kyle McMartin
2009-10-06 18:09 ` Randy Dunlap [this message]
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=20091006110941.eebe58af.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 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.