mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dan Merillat" <harik.attar@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kbuild + Cross compiling
Date: Fri, 5 May 2006 02:30:05 -0400	[thread overview]
Message-ID: <c0c067900605042330s2ebfea1fk8d218a5a826f67f9@mail.gmail.com> (raw)
In-Reply-To: <20060505045529.GA17896@mars.ravnborg.org>

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.
>
> 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

2.6.15, but make 3.80.  Is that the same problem?

I havn't developed on i386 lately so I don't know if it's only a
cross-compile issue.

  reply	other threads:[~2006-05-05  6:30 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 [this message]
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=c0c067900605042330s2ebfea1fk8d218a5a826f67f9@mail.gmail.com \
    --to=harik.attar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sam@ravnborg.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®