Re: [RFC PATCH 3/6] kbuild: convert include and source paths



On Mon, May 05, 2008 at 05:24:26PM +0200, Peter Oberparleiter wrote:
From: Peter Oberparleiter <peter.oberparleiter@xxxxxxxxxx>

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/



Relevant Pages

  • Re: [RFC PATCH 3/6] kbuild: convert include and source paths
    ... Modify kbuild to convert relative include and source paths to absolute ... Also change the module versioning mechanism to alter object file ... names only after compiling. ...
    (Linux-Kernel)
  • [RFC PATCH 3/6] kbuild: convert include and source paths
    ... Modify kbuild to convert relative include and source paths to absolute ... Also change the module versioning mechanism to alter object file ... names only after compiling. ...
    (Linux-Kernel)
  • [RFC PATCH 3/8] kbuild: convert include and source paths
    ... Modify kbuild to convert relative include and source paths to absolute ... Also change the module versioning mechanism to alter object file ... names only after compiling. ...
    (Linux-Kernel)
  • Re: Number of Objects in Static Link Library
    ... Up until this time, I've generated the libraries from object files that each represent a related group of functions and their data. ... The end result is that if a symbol in the object file is referenced, the entire object file is dragged in, even if just one function is referenced. ... With most linkers, the minimum amount that can normally be pulled in is one "module" or "translation unit". ... This normally corresponds to a single .o file that comes from either compiling a .c file or assembling an assembly-language file. ...
    (comp.unix.programmer)
  • Re: Driver linking error(symbols already defined), please help thi
    ... Compiling - shimmer.rc for i386 ... ning treated as error - no object file generated ... IST_ENTRY': macro redefinition ...
    (microsoft.public.development.device.drivers)