public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 06:55:29 +0200	[thread overview]
Message-ID: <20060505045529.GA17896@mars.ravnborg.org> (raw)
In-Reply-To: <c0c067900605041852m50e04171x7fd1579e77c9d5a3@mail.gmail.com>

On Thu, May 04, 2006 at 09:52:56PM -0400, Dan Merillat wrote:
> I must be an idiot, but why does Kbuild rebuild every file when 
> cross-compiling?
> I'm not editing .config or touching any headers, I'm making tweaks to
> a single .c driver,
> and it is taking forever due to continual full-rebuilds.
> 
> building on i386 for ARCH=arm CROSS_COMPILE=arm-linux-uclibc-
> 
> I tried following the logic, but everything is a forced build using
> if_changed and if_changed_dep, and I can't read GNU Make well enough
> to figure out what it thinks is new.  I know make -d says all the
> dependancies are up-to-date, so it's being forced some other way.
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.

Btw. what make version and what kernel version are you compiling?
There was some inconsistency in kbuild that triggered with make 3.81-rc1
and which will trigger with make 3.82-cvs also.
This issue was only fixed lately - recall it was for 2.6.16

	Sam

  reply	other threads:[~2006-05-05  4:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05  1:52 Kbuild + Cross compiling Dan Merillat
2006-05-05  4:55 ` Sam Ravnborg [this message]
2006-05-05  6:30   ` Dan Merillat
2006-05-05 15:15     ` Sam Ravnborg
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=20060505045529.GA17896@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