From: Sam Ravnborg <sam@ravnborg.org>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Adrian Bunk <bunk@kernel.org>,
peter.oberparleiter@de.ibm.com, linux-kernel@vger.kernel.org,
ltp-coverage@lists.sourceforge.net, oberparleiter@googlemail.com
Subject: Re: [PATCH 6/7] kbuild: make source and include paths absolute
Date: Fri, 23 May 2008 21:52:22 +0200 [thread overview]
Message-ID: <20080523195222.GA366@uranus.ravnborg.org> (raw)
In-Reply-To: <19f34abd0805231242r32892322n6c0a25e06d93ff96@mail.gmail.com>
> >>
> >> Well I guess that's understandable with O=.
> >>
> >> But I find it rather nasty. (I guess it'd be less nasty if I were to
> >> get off my butt and work out how to teach rxvt that "/" is a word
> >> separator).
> >>
> >> What do others think?
> >
> > That the gcov tool has a bug if it insist on using absolute paths.
> > And thus we should fix gcov and not workaround it in the kernel.
>
> IIRC, there was also the slight problem that all uses of __FILE__
> (there are quite a few in the kernel) will also now be absolute and
> increase the size of the vmlinux image by quite a bit.
>
> Yeah... http://lkml.org/lkml/2006/4/25/40
This is specific to O=.. build kernels.
I recall this is not an issue for the gcov patchset (if O=... is not used).
But I have not checked it.
Sam
next prev parent reply other threads:[~2008-05-23 19:52 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
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 [this message]
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=20080523195222.GA366@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp-coverage@lists.sourceforge.net \
--cc=oberparleiter@googlemail.com \
--cc=peter.oberparleiter@de.ibm.com \
--cc=vegard.nossum@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox