From: Jan Blunck <jblunck@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] kbuild: make source and include paths absolute
Date: Mon, 19 May 2008 13:45:29 +0000 (UTC) [thread overview]
Message-ID: <g0s09p$o7h$1@ger.gmane.org> (raw)
In-Reply-To: 48313E08.8070904@de.ibm.com
On Mon, 19 May 2008 10:44:56 +0200, Peter Oberparleiter wrote:
> From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
>
> Change all source and include paths to absolute form when
> CONFIG_GCOV_PROFILE is enabled.
>
> Example:
>
> gcc -Idir1 -c a.c -o a.o
>
> will become
>
> gcc -I/path/to/dir1 -c /path/to/a.c -o a.o
>
> Required by the gcov profiling infrastructure: when compiling with
> option -fprofile-arcs, gcc stores file names inside object files.
> Relative paths prevent the gcov tool from finding corresponding source
> files.
I think it would be good to fix this in the gcov tool. When I think
of distribution kernels the source usually ends up in a different
place in the packages than the kernel was originally compiled. So
it would be good to extend gcov here or let it search in well known
locations first (/usr/src/linux, /usr/src/debug/...).
Cheers,
Jan
next prev parent reply other threads:[~2008-05-19 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 8:44 [PATCH 6/7] kbuild: make source and include paths absolute Peter Oberparleiter
2008-05-19 13:45 ` Jan Blunck [this message]
2008-05-23 3:17 ` Andrew Morton
2008-05-23 17:18 ` Adrian Bunk
2008-05-23 18:17 ` Andrew Morton
2008-05-23 19:09 ` Sam Ravnborg
2008-05-23 19:42 ` Vegard Nossum
2008-05-23 19:52 ` Sam Ravnborg
2008-05-27 9:16 ` 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='g0s09p$o7h$1@ger.gmane.org' \
--to=jblunck@suse.de \
--cc=linux-kernel@vger.kernel.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