From: Herbert Xu <herbert@gondor.apana.org.au>
To: Borislav Petkov <bp@alien8.de>
Cc: Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
x86@kernel.org, linux-crypto@vger.kernel.org,
Tim Chen <tim.c.chen@linux.intel.com>
Subject: Re: randconfig build error with next-20131223, in arch/x86/crypto/aesni-intel_avx.S
Date: Mon, 30 Dec 2013 17:04:50 +0800 [thread overview]
Message-ID: <20131230090450.GA8636@gondor.apana.org.au> (raw)
In-Reply-To: <20131223160238.GA15360@pd.tnic>
On Mon, Dec 23, 2013 at 05:02:38PM +0100, Borislav Petkov wrote:
> 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.
Indeed. Tim, can you provide me with a fix for this?
Thanks,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
prev parent reply other threads:[~2013-12-30 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 15:09 randconfig build error with next-20131223, in arch/x86/crypto/aesni-intel_avx.S Jim Davis
2013-12-23 16:02 ` Borislav Petkov
2013-12-30 9:04 ` Herbert Xu [this message]
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=20131230090450.GA8636@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=bp@alien8.de \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jim.epost@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=tim.c.chen@linux.intel.com \
--cc=x86@kernel.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).