From: Michael Ellerman <mpe@ellerman.id.au>
To: linuxppc-dev@ozlabs.org
Cc: npiggin@gmail.com
Subject: [PATCH 2/5] powerpc/vdso64: Drop vdso64as
Date: Thu, 11 Aug 2016 16:03:12 +1000 [thread overview]
Message-ID: <1470895395-10007-2-git-send-email-mpe@ellerman.id.au> (raw)
In-Reply-To: <1470895395-10007-1-git-send-email-mpe@ellerman.id.au>
We can just use the standard .S -> .o rule, cmd_as_o_S.
That also fixes the bug we had in the vdso64as rule which is that it
didn't depend on FORCE, which it should have because it used
if_changed_dep.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
---
arch/powerpc/kernel/vdso64/Makefile | 6 ------
1 file changed, 6 deletions(-)
diff --git a/arch/powerpc/kernel/vdso64/Makefile b/arch/powerpc/kernel/vdso64/Makefile
index c710802b8fb6..1cf554258eb0 100644
--- a/arch/powerpc/kernel/vdso64/Makefile
+++ b/arch/powerpc/kernel/vdso64/Makefile
@@ -31,15 +31,9 @@ $(obj)/%.so: OBJCOPYFLAGS := -S
$(obj)/%.so: $(obj)/%.so.dbg FORCE
$(call if_changed,objcopy)
-# assembly rules for the .S files
-$(obj-vdso64): %.o: %.S
- $(call if_changed_dep,vdso64as)
-
# actual build commands
quiet_cmd_vdso64ld = VDSO64L $@
cmd_vdso64ld = $(CC) $(c_flags) -Wl,-T $^ -o $@
-quiet_cmd_vdso64as = VDSO64A $@
- cmd_vdso64as = $(CC) $(a_flags) -c -o $@ $<
# install commands for the unstripped file
quiet_cmd_vdso_install = INSTALL $@
--
2.7.4
next prev parent reply other threads:[~2016-08-11 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-11 6:03 [PATCH 1/5] powerpc/Makefile: CROSS32AS is unused, remove it Michael Ellerman
2016-08-11 6:03 ` Michael Ellerman [this message]
2016-08-11 6:03 ` [PATCH 3/5] powerpc/boot: Use $(Q) to quiet build rules not @ Michael Ellerman
2016-08-11 6:03 ` [PATCH 4/5] powerpc/Makefile: Drop CONFIG_WORD_SIZE for BITS Michael Ellerman
2016-08-11 6:03 ` [PATCH 5/5] powerpc/Makefile: Construct the UTS_MACHINE value more concisely Michael Ellerman
2016-09-13 12:16 ` [1/5] powerpc/Makefile: CROSS32AS is unused, remove it Michael Ellerman
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=1470895395-10007-2-git-send-email-mpe@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=npiggin@gmail.com \
/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).