From: Andrew Morton <akpm@linux-foundation.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org, oberparleiter@googlemail.com,
peter.oberparleiter@de.ibm.com, sam@ravnborg.org,
ltp-coverage@lists.sourceforge.net
Subject: Re: [PATCH 0/7] gcov kernel support
Date: Fri, 23 May 2008 15:23:11 -0700 [thread overview]
Message-ID: <20080523152311.1dde66a7.akpm@linux-foundation.org> (raw)
In-Reply-To: <7b1023f2a9cf769f8bc047c0116be9dd@kernel.crashing.org>
On Fri, 23 May 2008 23:52:43 +0200
Segher Boessenkool <segher@kernel.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.
next prev parent reply other threads:[~2008-05-23 22:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:42 Peter Oberparleiter
2008-05-19 11:42 ` Andi Kleen
2008-05-23 8:12 ` Andrew Morton
2008-05-23 11:06 ` Segher Boessenkool
2008-05-23 16:56 ` Andrew Morton
2008-05-23 21:52 ` Segher Boessenkool
2008-05-23 22:23 ` Andrew Morton [this message]
2008-05-27 8:32 ` Peter Oberparleiter
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=20080523152311.1dde66a7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=oberparleiter@googlemail.com \
--cc=peter.oberparleiter@de.ibm.com \
--cc=sam@ravnborg.org \
--cc=segher@kernel.crashing.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
Powered by JetHome