All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] SN makefile stuff
Date: Sat, 08 Mar 2003 09:56:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709806010@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805992@msgid-missing>

On Fri, Mar 07, 2003 at 05:13:41PM -0800, Jesse Barnes wrote:
> Does this look a little better?  Still can't figure out why fprom
> always rebuilds all files though...

What is included in the patch looks fine.
But you did not include arch/ia64/sn/fakeprom/Makefile this time??

To catch the reason why fprom rebuilds all (not all, but some I guess)
files follow these steps.

1) What file is the first being rebuild
- When one file is being rebuild obviously all files dependent on
  this one will be rebuild.
2) take a good look in the corresponding makefile
  - Is the target included in EXTRA_TARGETS without $(obj)/ prefix?
  - Is FORCE one of the prerequisites to the target?
    - Thats needed if you use $(call if_changed,{gzip,ld,objcopy}
3) Did you use a space in the $(call if_changed, ld)
                                                ^
$(call if_changed,ld)  <= correct
$(call if_changed, ld) <= wrong

4) ... Lots of other reasons. Send me the makefile in question off-line
   if you want an extra pair of eyes on it.

One unrelated question.
Would it be possible to use the mach- scheme as used for i386 for sn?
As it is done today it looks like a new architecture hidden
below arch/ia64/*.

	Sam


  parent reply	other threads:[~2003-03-08  9:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-06 22:53 [Linux-ia64] SN makefile stuff Jesse Barnes
2003-03-07  7:02 ` Sam Ravnborg
2003-03-08  1:13 ` Jesse Barnes
2003-03-08  9:56 ` Sam Ravnborg [this message]
2003-03-08 16:52 ` Jesse Barnes
2003-03-08 21:29 ` 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=marc-linux-ia64-105590709806010@msgid-missing \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.