From: Peter Oberparleiter <peter.oberparleiter@de.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ltp-list@lists.sourceforge.net,
ltp-coverage@lists.sourceforge.net, sam@ravnborg.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 3/6] kbuild: convert include and source paths
Date: Tue, 06 May 2008 19:28:39 +0200 [thread overview]
Message-ID: <48209547.7020807@de.ibm.com> (raw)
In-Reply-To: <20080505213251.d2025dc8.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Mon, 05 May 2008 17:24:26 +0200 Peter Oberparleiter <peter.oberparleiter@de.ibm.com> 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.
> It doesn't appear to affect __FILE__ in any way (which is good). But I'm
> unsure what it _does_ affect. The changelog implies that it will convert
> "liunx/foo.h" into /usr/src/linux/include/foo.h, only it doesn't.
>
> ho hum.
This patch should convert
gcc -Idir1 -c a.c -o a.o
to
gcc -I/path/to/dir1 -c /path/to/a.c -o a.o
As a standalone change this has no visible effect, but when gcc option
-fprofile-arcs is specified (as done in patch 5), the resulting object
files should only contain absolute paths.
Regards,
Peter
prev parent reply other threads:[~2008-05-06 17:28 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
2008-05-06 17:03 ` Peter Oberparleiter
2008-05-06 4:32 ` Andrew Morton
2008-05-06 17:28 ` Peter Oberparleiter [this message]
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=48209547.7020807@de.ibm.com \
--to=peter.oberparleiter@de.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=ltp-list@lists.sourceforge.net \
--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.