Re: [kbuild-devel] arch/i386/boot rebuilt on every compile...
Sam Ravnborg wrote: Seen it to - but were busy with other stuff. If you do a $ make V=2 Then you will notice that kbuild tells you that the .o files are built because they are not listed in $(targets). Thanks. That was the missing bit. Didn't know about V=2, that's quite handy. Reading the commonts in scripts/Kbuild.include it says: this is most likely a bug in your kbuild file. So I did the following and it cured it: Will merge. -hpa - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] arch/i386/boot rebuilt on every compile...
On Tue, Jul 17, 2007 at 10:27:22PM +0200, Sam Ravnborg wrote: On Tue, Jul 17, 2007 at 11:49:42AM -0700, H. Peter Anvin wrote: For some reason, everything in arch/i386/boot is rebuilt on every compile. It's not a huge time waster, but it has annoyed people enough that they ask me about it. version.o and setup.elf obviously would, since they contain a version string, but none of the other .o files have any obvious reason for being rebuild, and the .cmd files don't show any dependencies that I would expect to be revved for each revision. Help? Seen it to - but were busy with other stuff. If you do a $ make V=2 Then you will notice that kbuild tells you that the .o files are built because they are not listed in $(targets). Reading the commonts in scripts/Kbuild.include it says: this is most likely a bug in your kbuild file. So I did the following and it cured it: Also fine manual in the Documentation/kbuild states: |Note: It is a common mistake to forget the target := assignment, | resulting in the target file being recompiled for no | obvious reason. Now, Sam, see how people are trying to escape from the noise of the LKML. Yet you are not CC patches and anything here, e.g. .23 updates :( [PATCH] x86: do not recompile boot for each build Signed-off-by: Sam Ravnborg [EMAIL PROTECTED] - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
Re: [kbuild-devel] arch/i386/boot rebuilt on every compile...
Sam Ravnborg wrote: On Tue, Jul 17, 2007 at 10:49:48PM +0200, Oleg Verych wrote: Now, Sam, see how people are trying to escape from the noise of the LKML. Yet you are not CC patches and anything here, e.g. .23 updates :( I prefer to have kbuild stuff in the public aka lkml. I should reflect this in MAINTAINERS too. I agree that there is much less noise here at kbuild-devel mainly due to the excellent job of mec that filter away all spam. But then many kbuild matters have impact on a lot of people so lkml is the better place. As for the kbuild patches I have not tried to tell git send-emals that there are two receivers - maybe that would work I think it's entirely appropriate to factor off kbuild onto a separate list, as long as the announcement to do so is public enough and the list is available to the public. A lot of subsystems have separate mailing lists, because the volume on LKML is so high that people miss important stuff all the time. Of course, major announcements should go to LKML. -hpa - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ ___ kbuild-devel mailing list kbuild-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kbuild-devel
