LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"Leonidas S. Barbosa" <leosilva@linux.vnet.ibm.com>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: linux-next: Tree for Mar 11 (powerpc build failure due to vmx crypto code)
Date: Wed, 11 Mar 2015 19:43:22 -0700 [thread overview]
Message-ID: <5500FD4A.7050408@roeck-us.net> (raw)
In-Reply-To: <20150312012315.GA12660@gondor.apana.org.au>
On 03/11/2015 06:23 PM, Herbert Xu wrote:
> On Wed, Mar 11, 2015 at 08:47:17AM -0700, Guenter Roeck wrote:
>>
>> Building powerpc:allmodconfig:
>>
>> ERROR: ".aes_p8_cbc_encrypt" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".aes_p8_set_encrypt_key" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".aes_p8_set_decrypt_key" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".gcm_init_p8" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".aes_p8_decrypt" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".aes_p8_encrypt" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".gcm_ghash_p8" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>> ERROR: ".aes_p8_ctr32_encrypt_blocks" [drivers/crypto/vmx/vmx-crypto.ko] undefined!
>>
>> Those functions are called but don't seem to be defined anywhere.
>
> They are meant to be generated by the perl scripts in that directory.
> Can you take a look at why those perl scripts didn't run or didn't
> function correctly?
>
It looks like the perl scripts do run - I see the .S files, and I do see .o files created.
But I still get the error.
Looking into the object files, I see
$ nm vmx-crypto.o | grep aes_p8_cbc_encrypt
0000000000000680 t .aes_p8_cbc_encrypt
U .aes_p8_cbc_encrypt
00000000000000a8 D aes_p8_cbc_encrypt
$ nm aesp8-ppc.o | grep aes_p8_cbc_encrypt
0000000000000680 t .aes_p8_cbc_encrypt
0000000000000060 D aes_p8_cbc_encrypt
In the assembler source, I see
.globl aes_p8_cbc_encrypt
but no .globl for .aes_p8_cbc_encrypt.
Does that tell you anything ?
I also notice is that the .S files are not removed with "make mrproper"
but left behind. Seems to me that those files should be removed.
Guenter
next prev parent reply other threads:[~2015-03-12 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 5:35 linux-next: Tree for Mar 11 Stephen Rothwell
2015-03-11 15:47 ` linux-next: Tree for Mar 11 (powerpc build failure due to vmx crypto code) Guenter Roeck
2015-03-12 1:23 ` Herbert Xu
2015-03-12 2:43 ` Guenter Roeck [this message]
2015-03-12 3:28 ` Herbert Xu
2015-03-12 3:51 ` Guenter Roeck
2015-03-12 3:53 ` Herbert Xu
2015-03-12 15:27 ` Leonidas S. Barbosa
2015-03-11 15:51 ` linux-next: Tree for Mar 11 (arm build failure, ASoC) Guenter Roeck
2015-03-12 6:53 ` Peter Ujfalusi
2015-03-11 15:55 ` linux-next: Tree for Mar 11 (arm:multi_v5_defconfig build failure) Guenter Roeck
2015-03-11 16:21 ` Simon Guinot
2015-03-11 16:26 ` Gregory CLEMENT
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=5500FD4A.7050408@roeck-us.net \
--to=linux@roeck-us.net \
--cc=herbert@gondor.apana.org.au \
--cc=leosilva@linux.vnet.ibm.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--subject='Re: linux-next: Tree for Mar 11 (powerpc build failure due to vmx crypto code)' \
/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
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).