linux-kernel - Re: [PATCH 0/7] gcov kernel support

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:	Fri, 23 May 2008 15:23:11 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Segher Boessenkool <segher@...nel.crashing.org>
Cc:	linux-kernel@...r.kernel.org, oberparleiter@...glemail.com,
	peter.oberparleiter@...ibm.com, sam@...nborg.org,
	ltp-coverage@...ts.sourceforge.net
Subject: Re: [PATCH 0/7] gcov kernel support

On Fri, 23 May 2008 23:52:43 +0200
Segher Boessenkool <segher@...nel.crashing.org> wrote:

> >> You *can* build with a non-biarch compiler, but then you need to point
> >> the kernel build system at a 32-bit toolchain to use for the 32-bit
> >> parts (via CROSS32_COMPILE).
> >
> > Jens built this one, using crosstool.  It is
> > http://userweb.kernel.org/~akpm/cross-compilers/power64-cross.tar.bz2
> >
> > It was all working happily until gcov came along :(
> 
> You were lucky, yes.  If your compiler would have been just a little
> bit older it wouldn't have been able to build 32-bit at all.
> 
> Do you have a separate 32-bit PowerPC compiler?

I dont' cross-compile for 32-bit power.  This is all 64-bit stuff.

>  If so, just set
> CROSS32_COMPILE to it; if not, you'll need a new toolchain.  In
> that case, it's probably worthwhile to upgrade to 4.1.2 at least...

Sigh.  Life's too short.  I'll go back to testing powerpc builds on the
powerpc box.

--
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/