public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.14-rc1 ia64 rebuilds everything every time
Date: Tue, 13 Sep 2005 19:44:29 +0000	[thread overview]
Message-ID: <20050913194429.GA18319@mars.ravnborg.org> (raw)
In-Reply-To: <23363.1126593124@kao2.melbourne.sgi.com>

On Tue, Sep 13, 2005 at 07:34:44PM +1000, Peter Chubb wrote:
> >>>>> "Keith" = Keith Owens <kaos@sgi.com> writes:
> 
> 
> Keith> Best solution: remove (and forbid) recursive definitions in
> Keith> asm-offset.c.
> 
> Unfortunately,I'm not sure that's possible.
> 
> 
> Keith> Kludge 2: Build arch/$(ARCH)/kernel/asm-offsets.s as a
> Keith> temporary file then check if it has changed or not, only
> Keith> updating the real arch/$(ARCH)/kernel/asm-offsets.s if there is
> Keith> any change.
> 
> This is what used to happen.
What actually used to happen was that asm-offsets.h seldom was rebuild
despite included file had changed in the meantime.
When it then got rebuild - then we did the "has file changed" trick.

That I can be convinced to add back. On the other hand this is no more
special than any other fundamental .h file - when it changes we
recompile was uses it.


The reason why it hit us hard with ia64 is that is gets rebuild due to
the circular dependency where the file used to build asm-offsets.h uses
asm-offsets.h.
If we solve that problem the 'recompile everything' issue disappear.

Tony already posted an ugly patch to solve most of this.
I agree fully with Tony this is an ugly patch - did I have better
ideas how to solve it I would have posted a patch.

	Sam

      parent reply	other threads:[~2005-09-13 19:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  6:32 2.6.14-rc1 ia64 rebuilds everything every time Keith Owens
2005-09-13  9:34 ` Peter Chubb
2005-09-13 19:44 ` Sam Ravnborg [this message]

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=20050913194429.GA18319@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-ia64@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