From mboxrd@z Thu Jan 1 00:00:00 1970 From: ard.biesheuvel@linaro.org (Ard Biesheuvel) Date: Thu, 24 Jul 2014 14:53:49 +0200 Subject: [PATCH] arm64/crypto: fix makefile rule for aes-glue-%.o In-Reply-To: References: Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 24 July 2014 14:35, Ard Biesheuvel wrote: > On 24 July 2014 14:29, Andreas Schwab wrote: >> Ard Biesheuvel writes: >> >>> On 30 June 2014 15:56, Andreas Schwab wrote: >>>> Ard Biesheuvel writes: >>>> >>>>> Out of curiosity, how did you trigger this failure? I have build this >>>>> code numerous times (and so have others) and I have never seen this >>>>> failure. >>>> >>>> Did you ever start with a clean tree? >>>> >>> >>> Yep, building both in-tree and out-of-tree, no trouble at all. >> >> So you probably didn't configure them as modules. >> > > Yes, all the time, in fact. They have now been added as built-ins to > the defconfig, but I always build as modules, because it is far easier > when developing. Also, looking into this a bit more, in my case I do see arch/arm64/crypto/.aes-glue-ce.o.cmd containing the command line and the full set of include/config/... rules that are used to track dependencies on the configuration. So what strikes me as odd is this: > CC [M] arch/arm64/crypto/aes-glue-ce.o > ld: cannot find arch/arm64/crypto/aes-glue-ce.o: No such file or directory so it seems make is perfectly happy to create the aes-glue-ce.o file, but the subsequent ld that uses it as input cannot find it. Perhaps the dependencies are screwed up elsewehere? Are there any other circumstances of interest? How many threads are you building in parallel? Other steps to reproduce? -- Ard.