[kbuild-devel] several small things (Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine)
* Fri, 25 Aug 2006 09:26:54 +0200 read.o - read.c It will only do this if you ask for it. The question was what happened when you did make read.o foo.o - foo.c bar.o - bar.c built-in.o - read.c foo.c bar.c (cf. default current: built-in.o - read.o foo.o bar.o) And this discussion is btw. mood. If the general opinion is that we shall include the -combine support all the kbuild infrastructure will anyway be redone. There are several small things that are not addressed in todays implementation and that will be fixed one way or the other. Did they get addressed year later or not? What they were (are)? Sam - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
[kbuild-devel] spelld: several small things
On Thu, Sep 20, 2007 at 02:15:57AM +0200, Oleg Verych wrote: * Fri, 25 Aug 2006 09:26:54 +0200 read.o - read.c It will only do this if you ask for it. The question was what happened when you did make read.o foo.o - foo.c bar.o - bar.c built-in.o - read.c foo.c bar.c (cf. default current: built-in.o - read.o foo.o bar.o) And this discussion is btw. mood. If the general opinion is that we shall include the -combine support all the kbuild infrastructure will anyway be redone. There are several small things that are not addressed in todays implementation and that will be fixed one way or the other. Did they get addressed year later or not? What they were (are)? Actually Were they got addressed? - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
