linux-kernel - Re: [patch] perf build questions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 Oct 2009 11:09:41 -0700
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Kyle McMartin <kyle@...artin.ca>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	lkml <linux-kernel@...r.kernel.org>,
	Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>
Subject: Re: [patch] perf build questions

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/