archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <>
To: "David S . Miller" <>
Cc:,,, Guenter Roeck <>,
	Masahiro Yamada <>,
	Marc Zyngier <>
Subject: [PATCH] sparc: vdso: Fix build failure seen due to kbuild changes
Date: Sun, 10 Nov 2019 17:11:06 -0800	[thread overview]
Message-ID: <> (raw)

sparc64:allmodconfig fails to build with the following error.

unrecognized e_machine 18 arch/sparc/vdso/vdso32/vclock_gettime.o
arch/sparc/vdso/vdso32/vclock_gettime.o: failed
make[2]: *** [arch/sparc/vdso/vdso32/vclock_gettime.o] Error 1
make[2]: *** Deleting file 'arch/sparc/vdso/vdso32/vclock_gettime.o'
make[2]: *** Waiting for unfinished jobs....

The problem bisects to commit a3de7a72c517 ("kbuild: change
*FLAGS_<basetarget>.o to take the path relative to $(obj)").
Duplicate the x86 specific defines from this commit to the sparc
vdso Makefile to fix the problem.

Fixes: a3de7a72c517 ("kbuild: change *FLAGS_<basetarget>.o to take the path relative to $(obj)")
Cc: Masahiro Yamada <>
Cc: Marc Zyngier <>
Signed-off-by: Guenter Roeck <>
 arch/sparc/vdso/Makefile | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/sparc/vdso/Makefile b/arch/sparc/vdso/Makefile
index 324a23947585..cb72a205cd7e 100644
--- a/arch/sparc/vdso/Makefile
+++ b/arch/sparc/vdso/Makefile
@@ -67,6 +67,7 @@ $(vobjs): KBUILD_CFLAGS := $(filter-out $(GCC_PLUGINS_CFLAGS) $(SPARC_REG_CFLAGS
 CFLAGS_REMOVE_vdso-note.o = -pg
 CFLAGS_REMOVE_vclock_gettime.o = -pg
+CFLAGS_REMOVE_vdso32/vclock_gettime.o = -pg
 $(obj)/ OBJCOPYFLAGS := -S
 $(obj)/ $(obj)/ FORCE
@@ -74,6 +75,7 @@ $(obj)/ $(obj)/ FORCE = $( = -m elf32_sparc -soname
+VDSO_LDFLAGS_vdso32/ = -m elf32_sparc -soname
 #This makes sure the $(obj) subdirectory exists even though vdso32/
 #is not a kbuild sub-make subdirectory

             reply	other threads:[~2019-11-11  1:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  1:11 Guenter Roeck [this message]
2019-11-11  1:32 ` [PATCH] sparc: vdso: Fix build failure seen due to kbuild changes David Miller
2019-11-11  1:47   ` Masahiro Yamada
2019-11-11 14:35     ` Guenter Roeck
2019-11-12 12:06       ` Masahiro Yamada

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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).