From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Merillat <harik.attar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kbuild + Cross compiling
Date: Fri, 5 May 2006 17:15:31 +0200 [thread overview]
Message-ID: <20060505151531.GB6568@mars.ravnborg.org> (raw)
In-Reply-To: <c0c067900605042330s2ebfea1fk8d218a5a826f67f9@mail.gmail.com>
On Fri, May 05, 2006 at 02:30:05AM -0400, Dan Merillat wrote:
> On 5/5/06, Sam Ravnborg <sam@ravnborg.org> wrote:
> >kbuild checks for any differences in the commandline alos - so a rebuild
> >happens if you change options to gcc (think -O2 => -Os).
> >If you experience that for example mm/slab.c is rebuild then try to
> >do the following:
> >cp mm/.slab.o.cmd foo
> >make mm/
> >diff -u foo mm/.slab.o.cmd
> >
> >If diff detects any difference then you know why and need to find out
> >why there is a difference.
>
> Nothing, even md5sums match.
> 2abfcbee132335ba8e1da120569abf67 .do_mounts.o.cmd
> 2abfcbee132335ba8e1da120569abf67 .do_mounts.o.cmd.1
>
> but it gets rebuilt every time.
So we need to dive a bit deeper to understand why everything gets
rebuild.
Try following patch:
diff --git a/scripts/Makefile.build b/scripts/Makefile.build
index e48e60d..4c52131 100644
--- a/scripts/Makefile.build
+++ b/scripts/Makefile.build
@@ -189,6 +189,9 @@ endef
# Built-in and composite module parts
%.o: %.c FORCE
+ @echo $@
+ @echo chg=$?
+ @echo arg-check=$(call arg-check, $(cmd_cc_o_c), $(cmd_$@))
$(call cmd,force_checksrc)
$(call if_changed_rule,cc_o_c)
This will not fix anything - but will give us a hint why things gets
rebuild.
After applying the patch try:
make init/do_mounts.o
And then post the output.
Also include the .do_mounts.o.cmd file
Sam
next prev parent reply other threads:[~2006-05-05 15:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 1:52 Dan Merillat
2006-05-05 4:55 ` Sam Ravnborg
2006-05-05 6:30 ` Dan Merillat
2006-05-05 15:15 ` Sam Ravnborg [this message]
2006-05-05 9:56 ` Ben Dooks
2006-05-05 14:36 ` Martin Schwidefsky
2006-05-05 20:53 ` Dan Merillat
2006-05-05 21:18 ` Sam Ravnborg
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=20060505151531.GB6568@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=harik.attar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®