From: Sam Ravnborg <sam@ravnborg.org>
To: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, ltp-list@lists.sourceforge.net,
ltp-coverage@lists.sourceforge.net,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH 3/6] kbuild: convert include and source paths
Date: Mon, 5 May 2008 21:58:15 +0200 [thread overview]
Message-ID: <20080505195815.GD8868@uranus.ravnborg.org> (raw)
In-Reply-To: <481F26AA.4050701@de.ibm.com>
On Mon, May 05, 2008 at 05:24:26PM +0200, Peter Oberparleiter wrote:
> From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
>
> Modify kbuild to convert relative include and source paths to absolute
> form. Also change the module versioning mechanism to alter object file
> names only after compiling.
>
> Required by the gcov profiling infrastructure: source paths are
> referenced by the compiled object files. Using relative paths or
> object file names which are different from the source name would
> prevent the gcov tool from finding the corresponding source files.
For the relative path issue do you really fix this at the right place?
I would say that teaching gcov tool from where to look would be better.
> Also change the module versioning mechanism to alter object file
> names only after compiling.
Can I get this as a separate patch please.
It may be general useful and makes sense to look at alone.
Sam
next prev parent reply other threads:[~2008-05-05 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 15:24 [RFC PATCH 3/6] kbuild: convert include and source paths Peter Oberparleiter
2008-05-05 19:58 ` Sam Ravnborg [this message]
2008-05-06 17:03 ` Peter Oberparleiter
2008-05-06 4:32 ` Andrew Morton
2008-05-06 17:28 ` 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=20080505195815.GD8868@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
--cc=peter.oberparleiter@de.ibm.com \
/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.