All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:06:00 +0200	[thread overview]
Message-ID: <ab1f935148982762bae55734ffb8acc7@kernel.crashing.org> (raw)
In-Reply-To: <20080523011213.690363c7.akpm@linux-foundation.org>

>> This is version #2 of the gcov kernel support patch set
>
> powerpc blew up:
>
> /opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/lib/ 
> gcc/powerpc64-unknown-linux-gnu/4.1.0/../../../../powerpc64-unknown- 
> linux-gnu/bin/ld: skipping incompatible  
> /opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/lib/ 
> gcc/powerpc64-unknown-linux-gnu/4.1.0/./libgcov.a when searching for  
> -lgcov
> /opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/lib/ 
> gcc/powerpc64-unknown-linux-gnu/4.1.0/../../../../powerpc64-unknown- 
> linux-gnu/bin/ld: cannot find -lgcov
> collect2: ld returned 1 exit status
> make[2]: *** [arch/powerpc/kernel/vdso32/vdso32.so.dbg] Error 1
> make[1]: *** [arch/powerpc/kernel/vdso32] Error 2

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 .

What does

/opt/crosstool/gcc-4.1.0-glibc-2.3.6/powerpc64-unknown-linux-gnu/bin/ 
powerpc64-unknown-linux-gnu-gcc -v

say?  (Or whatever the correct path to that compiler is, the directory
structure is a bit unusual here it seems).  There shouldn't be a
--disable-biarch there.

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).


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).


Segher


  reply	other threads:[~2008-05-23 11:09 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 [this message]
2008-05-23 16:56     ` Andrew Morton
2008-05-23 21:52       ` Segher Boessenkool
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=ab1f935148982762bae55734ffb8acc7@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 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.