linux-kernel - Re: randconfig build error with next-20131223, in arch/x86/crypto/aesni-intel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 23 Dec 2013 17:02:38 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Jim Davis <jim.epost@...il.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Herbert Xu <herbert@...dor.apana.org.au>,
	"David S. Miller" <davem@...emloft.net>, tglx@...utronix.de,
	mingo@...hat.com, hpa@...or.com, x86@...nel.org,
	linux-crypto@...r.kernel.org, Tim Chen <tim.c.chen@...ux.intel.com>
Subject: Re: randconfig build error with next-20131223, in
 arch/x86/crypto/aesni-intel_avx.S

On Mon, Dec 23, 2013 at 08:09:18AM -0700, Jim Davis wrote:
> Building with the attached random configuration file,
> 
> arch/x86/crypto/aesni-intel_avx.S: Assembler messages:
> arch/x86/crypto/aesni-intel_avx.S:1449: Error: bad register name `%r12'
> [...]
> arch/x86/crypto/aesni-intel_avx.S:2807: Error: bad register name `%r12'
> make[2]: *** [arch/x86/crypto/aesni-intel_avx.o] Error 1

> #
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86 3.13.0-rc5 Kernel Configuration
> #
> # CONFIG_64BIT is not set
> CONFIG_X86_32=y

Sounds like this aesni-intel_avx.S thing wasn't meant to be built for
32-bit.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/