All of lore.kernel.org
 help / color / mirror / Atom feed
From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: arch/arm64/efi-stub.o rebuilding every time?
Date: Thu, 3 Jul 2014 15:13:42 +0100	[thread overview]
Message-ID: <20140703141342.GB14305@arm.com> (raw)

Hi guys,

If I build an arm64 kernel, then simply hit make again without changing
anything, I find that efi-stub.o is rebuilt every time (with an annoying
warning too, but I think you already know about that):


$ make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- -j8 Image
  CHK     include/config/kernel.release
  CHK     include/generated/uapi/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/generated/compile.h
  CC      arch/arm64/kernel/efi-stub.o
In file included from arch/arm64/kernel/efi-stub.c:44:0:
arch/arm64/kernel/../../../drivers/firmware/efi/fdt.c: In function ?update_fdt?:
arch/arm64/kernel/../../../drivers/firmware/efi/fdt.c:66:22: warning: unused variable ?name? [-Wunused-variable]
   const char *type, *name;
                      ^
  CHK     kernel/config_data.h
  LD      arch/arm64/kernel/built-in.o
  LINK    vmlinux
  LD      vmlinux.o
  MODPOST vmlinux.o
  GEN     .version
  CHK     include/generated/compile.h
  UPD     include/generated/compile.h
  CC      init/version.o
  LD      init/built-in.o
  KSYM    .tmp_kallsyms1.o
  KSYM    .tmp_kallsyms2.o
  LD      vmlinux
  SORTEX  vmlinux
  SYSMAP  System.map
  OBJCOPY arch/arm64/boot/Image


Does this actually need to be rebuilt, or is there a buggy Makefile
somewhere?

Will

             reply	other threads:[~2014-07-03 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 14:13 Will Deacon [this message]
2014-07-03 14:16 ` arch/arm64/efi-stub.o rebuilding every time? Ard Biesheuvel
2014-07-04  6:36   ` Matt Fleming
2014-07-04  8:24     ` Will Deacon
2014-07-04  8:53       ` Ard Biesheuvel

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=20140703141342.GB14305@arm.com \
    --to=will.deacon@arm.com \
    --cc=linux-arm-kernel@lists.infradead.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.