From: schwab@suse.de (Andreas Schwab)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o
Date: Mon, 30 Jun 2014 15:14:33 +0200 [thread overview]
Message-ID: <mvmvbri4k06.fsf@hawking.suse.de> (raw)
This fixes the following build failure:
CC [M] arch/arm64/crypto/aes-glue-ce.o
ld: cannot find arch/arm64/crypto/aes-glue-ce.o: No such file or directory
scripts/Makefile.build:393: recipe for target 'arch/arm64/crypto/aes-ce-blk.o' failed
make[1]: *** [arch/arm64/crypto/aes-ce-blk.o] Error 1
Makefile:893: recipe for target 'arch/arm64/crypto' failed
make: *** [arch/arm64/crypto] Error 2
The $(obj)/aes-glue-%.o rule only creates $(obj)/.tmp_aes-glue-ce.o, it
should use if_changed_rule instead of if_changed_dep.
Signed-off-by: Andreas Schwab <schwab@suse.de>
---
arch/arm64/crypto/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm64/crypto/Makefile b/arch/arm64/crypto/Makefile
index 2070a56..a3f935f 100644
--- a/arch/arm64/crypto/Makefile
+++ b/arch/arm64/crypto/Makefile
@@ -35,4 +35,4 @@ AFLAGS_aes-neon.o := -DINTERLEAVE=4
CFLAGS_aes-glue-ce.o := -DUSE_V8_CRYPTO_EXTENSIONS
$(obj)/aes-glue-%.o: $(src)/aes-glue.c FORCE
- $(call if_changed_dep,cc_o_c)
+ $(call if_changed_rule,cc_o_c)
--
2.0.1
--
Andreas Schwab, SUSE Labs, schwab at suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next reply other threads:[~2014-06-30 13:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 13:14 Andreas Schwab [this message]
2014-06-30 13:38 ` [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o Ard Biesheuvel
2014-06-30 13:56 ` Andreas Schwab
2014-06-30 14:08 ` Ard Biesheuvel
2014-07-24 12:29 ` Andreas Schwab
2014-07-24 12:35 ` Ard Biesheuvel
2014-07-24 12:53 ` Ard Biesheuvel
2014-07-24 13:26 ` Andreas Schwab
2014-07-24 13:29 ` Ard Biesheuvel
2014-07-24 13:40 ` Andreas Schwab
2014-07-24 14:18 ` Ard Biesheuvel
2014-07-24 14:24 ` Ard Biesheuvel
2014-07-24 16:12 ` Sam Ravnborg
2014-07-24 19:25 ` Ard Biesheuvel
2014-07-24 20:45 ` Sam Ravnborg
2014-07-25 6:28 ` Ard Biesheuvel
2014-07-27 18:40 ` Sam Ravnborg
2014-07-28 17:00 ` Ard Biesheuvel
2014-07-28 19:06 ` Sam Ravnborg
2014-07-24 16:03 Ard Biesheuvel
2014-07-24 16:47 ` Catalin Marinas
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=mvmvbri4k06.fsf@hawking.suse.de \
--to=schwab@suse.de \
--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 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).