kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: martink@posteo.de (Martin Kepplinger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Rebuild a changed kernel quickly with make?
Date: Thu, 04 Jul 2013 14:59:42 +0200	[thread overview]
Message-ID: <51D571BE.4010101@posteo.de> (raw)
In-Reply-To: <CABdVeABMTob+rSKXvrdnWsJTVCbOKpheU5DquM2H-AbnmQyyHA@mail.gmail.com>

On 04.07.2013 11:13, David kiarie wrote:
> 
> 
> On Thu, Jul 4, 2013 at 9:53 AM, Warlich, Christof
> <christof.warlich at siemens.com <mailto:christof.warlich@siemens.com>> wrote:
> 
>     > When I change something in the kernel and just hit make from toplevel
>     > dir, it always compiles everything again, no matter if it wasn't
>     changed
>     > at all in the meantime.
>     > I thought make should be able to make a second build time really
>     quick.
>     > What am I doing wrong? Is there a make target I don't know of? I don't
>     > type in any, just make.
> 
>     Are you sure it rebuilds _everything_, i.e. as in a fresh build or
>     after a "make clean?"
> 
>     When I rerun make without changing anything, it just does the
>     following, which is much
>     Less than a complete build:
> 
>     $ make
>     make -C /root/views/DCUOS_3/derived/tdc/kernel
>     O=/root/views/DCUOS_3/derived/tdc/kernelObjects/.
>       Using /root/views/DCUOS_3/derived/tdc/kernel as source for kernel
>       GEN     /root/views/DCUOS_3/derived/tdc/kernelObjects/Makefile
>       CHK     include/linux/version.h
>       CHK     include/linux/utsrelease.h
>       SYMLINK include/asm -> include/asm-x86
>       CALL  
>      /root/views/DCUOS_3/derived/tdc/kernel/scripts/checksyscalls.sh
>       CHK     include/linux/compile.h
>       VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
>       VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
>       VDSOSYM arch/x86/vdso/vdso32-syms.lds
>       LD      arch/x86/vdso/built-in.o
>       LD      arch/x86/built-in.o
>       LD      vmlinux.o
>       MODPOST vmlinux.o
>       GEN     .version
>       CHK     include/linux/compile.h
>       UPD     include/linux/compile.h
>       CC      init/version.o
>       LD      init/built-in.o
>       LD      .tmp_vmlinux1
>       KSYM    .tmp_kallsyms1.S
>       AS      .tmp_kallsyms1.o
>       LD      .tmp_vmlinux2
>       KSYM    .tmp_kallsyms2.S
>       AS      .tmp_kallsyms2.o
>       LD      vmlinux
>       SYSMAP  System.map
>       SYSMAP  .tmp_System.map
>       VOFFSET arch/x86/boot/voffset.h
>       OBJCOPY arch/x86/boot/compressed/vmlinux.bin
>       GZIP    arch/x86/boot/compressed/vmlinux.bin.gz
>       MKPIGGY arch/x86/boot/compressed/piggy.S
>       AS      arch/x86/boot/compressed/piggy.o
>       LD      arch/x86/boot/compressed/vmlinux
>       ZOFFSET arch/x86/boot/zoffset.h
>       AS      arch/x86/boot/header.o
>       CC      arch/x86/boot/version.o
>       LD      arch/x86/boot/setup.elf
>       OBJCOPY arch/x86/boot/setup.bin
>       OBJCOPY arch/x86/boot/vmlinux.bin
>       BUILD   arch/x86/boot/bzImag
>     Setup is 11148 bytes (padded to 11264 bytes).
>     System is 1759 kB
>     CRC f583db84
>     Kernel: arch/x86/boot/bzImage is ready  (#3)
>       Building modules, stage 2.
>       MODPOST 1 modules
>     _______________________________________________
>     Kernelnewbies mailing list
>     Kernelnewbies at kernelnewbies.org <mailto:Kernelnewbies@kernelnewbies.org>
>     http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 
> Am also pretty sure it does not compile everything.
> 
> 
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> 
indeed it doesn't compile everything but a lot (or all?) modules for
example. A build with very little changes lasts more than half the time
a fresh clean build lasts. But I don't seem to do anything wrong then,
just wanted to check if I can do something about it. thanks!!

                 martin

  reply	other threads:[~2013-07-04 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-04  6:33 Rebuild a changed kernel quickly with make? Martin Kepplinger
2013-07-04  6:53 ` Warlich, Christof
2013-07-04  9:13   ` David kiarie
2013-07-04 12:59     ` Martin Kepplinger [this message]
2013-07-04 18:18 ` Valdis.Kletnieks at vt.edu
2013-07-09  7:46 ` Srinivas Ganji
2013-07-09 14:21   ` Valdis.Kletnieks at vt.edu

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=51D571BE.4010101@posteo.de \
    --to=martink@posteo.de \
    --cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).