mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: empty kbuild rebuilding all 2.6.13-mm3 ia64 sn2
Date: Fri, 16 Sep 2005 01:54:12 -0700	[thread overview]
Message-ID: <20050916015412.002642a4.pj@sgi.com> (raw)

Using 2.6.13-mm3, building for SN2 (an ia64 arch) using sn2_defconfig,
after doing a full successful build, if I just issue another 'make',
it builds more or less every file all over again.  When I am just
working in one *.c file, this causes make to be much more expensive
than it should, rebuilding everything, instead of just that one file
and relinking (or close to that).

No doubt you will need some additional information, unless I get
lucky and you recognize the problem already.

But I don't know what you will be needing, so I'll just have to
wait for the request.

And there is a good chance that it's something bogus on my end.
I say this simply because I don't notice anyone else complaining
about this on lkml, so quite possibly it's just me seeing this.

An empty make begins with:

  CHK     include/linux/version.h
  CC      arch/ia64/kernel/asm-offsets.s
  GEN     include/asm-ia64/asm-offsets.h
  CHK     usr/initramfs_list
  CC      init/main.o
  CC      arch/ia64/mm/init.o
  AS      arch/ia64/ia32/ia32_entry.o
  CC      arch/ia64/sn/kernelsetup.o

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

             reply	other threads:[~2005-09-16  8:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16  8:54 Paul Jackson [this message]
2005-09-16 13:35 ` 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=20050916015412.002642a4.pj@sgi.com \
    --to=pj@sgi.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®