From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Peter Oberparleiter <oberparleiter@googlemail.com>,
Peter Oberparleiter <peter.oberparleiter@de.ibm.com>,
Sam Ravnborg <sam@ravnborg.org>,
ltp-coverage@lists.sourceforge.net
Subject: Re: [PATCH 0/7] gcov kernel support
Date: Fri, 23 May 2008 23:52:43 +0200 [thread overview]
Message-ID: <7b1023f2a9cf769f8bc047c0116be9dd@kernel.crashing.org> (raw)
In-Reply-To: <20080523095623.5678a34f.akpm@linux-foundation.org>
>> Sounds like your toolchain was built without biarch support, but
>> you're
>> using it for the 32-bit parts of the kernel anyway. Which works as
>> long
>> as you're not using any libraries, but now you need libgcov.a .
>
> ok..
>
>> What does
>>
>> /opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/
>> powerpc64-unknown-linux-gnu-gcc -v
>>
>> say?
>
> y:/home/akpm>
> /opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/
> powerpc64-unknown-linux-gnu-gcc -v
> Using built-in specs.
> Target: powerpc64-unknown-linux-gnu
> Configured with:
> /home/axboe/crosstool-0.43/build/powerpc64-unknown-linux-gnu/gcc
> -4.1.0-glibc-2.3.6/gcc-4.1.0/configure
> --target=powerpc64-unknown-linux-gnu
> --host=x86_64-host_unknown-linux-gnu
> --prefix=/opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-
> gnu
> --disable-multilib
That's the culprit. I believe 4.1.0 enables multilib by default on
PowerPC
compilers that target 64-bit by default (the patch for that is dated
almost
a full year before the 4.1.0 release). I have no idea why crosstool
disables this support; perhaps there were some problems with some older
GCC version (or this one, even; it's ancient as well).
>> Or, what does
>>
>> find
>> /opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/
>> 4.1.0/
>> -name libgcov.a
>>
>> say? (It should usually find three versions: 64-bit, 32-bit, 32-bit
>> no
>> float).
>
> Only a single hit:
Right, as expected.
>> 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? 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...
Segher
next prev parent reply other threads:[~2008-05-23 21:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:42 [PATCH 0/7] gcov kernel support 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 [this message]
2008-05-23 22:23 ` Andrew Morton
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=7b1023f2a9cf769f8bc047c0116be9dd@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=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 \
/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