On Sun, May 12, 2002 at 09:38:48AM +1000, Keith Owens wrote:
> Any reason that you are using sed and not cpp like the other
Only historical and a hatred of cpp's "# line file" stuff, and the fact
that ARM needs to use sed elsewhere in the build to get around broken
GCC %c0 stuff.
I think we could actually get rid of the preprocessing of the linker
files - see ld's defsym argument.
> The use and name of linker scripts varies across architectures, some
> use cpp, some use sed, some do not pre-process at all. This makes it
> awkward for repositories and dont-diff lists, they need special rules
> for every architecture. In kbuild 2.5 I am trying to standardize on
> arch/$(ARCH)/vmlinux.lds.S which is always pre-processed by cpp to
> vmlinux.lds.i which is used to link vmlinux.
Eww, so I can't use "find . -name '*.[cS]'" to find all the C source and
assembly source with kbuild 2.5 because we've got pollution of the .S
> Using .S -> .i has three benefits. The file name and the code for
> converting the file is standardized. Dont-diff lists exclude *.[oais]
> files, no need for special cases for each architecture.
I'm not a fan of dont-diff stuff myself - I'd rather ensure a clean
source tree and then diff rather than diffing a dirty built tree.
dont-diff stuff needs to be maintained and extended as stuff changes
in the kernel tree, and lets face it, no amount of extension pollution
will prevent it from being updated over time.
-- Russell King (email@example.com) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue May 14 2002 - 12:00:17 EST