From: Jens Axboe <axboe@kernel.dk>
To: Aaron Carroll <aaronc@cse.unsw.edu.au>
Cc: fio@vger.kernel.org
Subject: Re: Build error in Android/x86
Date: Fri, 15 Mar 2013 17:10:29 +0100 [thread overview]
Message-ID: <20130315161029.GV31875@kernel.dk> (raw)
In-Reply-To: <5142C392.5050302@cse.unsw.edu.au>
On Fri, Mar 15 2013, Aaron Carroll wrote:
> I'm trying to build FIO with an Android/x86 cross compiler:
>
> make CROSS_COMPILE=~/dev/android-toolchains-r8c/x86-4.6/bin/i686-linux-android-
>
> but get the following error:
>
> arch/arch-x86-common.h:9:2: error: inconsistent operand constraints in an 'asm'
>
> which is complaining about this function:
>
> static inline void do_cpuid(unsigned int *eax, unsigned int *ebx,
> unsigned int *ecx, unsigned int *edx)
> {
> asm volatile("cpuid"
> : "=a" (*eax), "=b" (*ebx), "=c" (*ecx), "=d" (*edx)
> : "0" (*eax), "2" (*ecx)
> : "memory");
> }
>
> Unfortunately I don't do x86 ASM. I'm wondering if this is a genuine error,
> or if something has broken in the cross compile.
Hmm, I wonder why it complains about that, looks legit to me... Maybe
it's the ecx being both input and output it doesn't like?
--
Jens Axboe
prev parent reply other threads:[~2013-03-15 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 6:45 Build error in Android/x86 Aaron Carroll
2013-03-15 16:10 ` Jens Axboe [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=20130315161029.GV31875@kernel.dk \
--to=axboe@kernel.dk \
--cc=aaronc@cse.unsw.edu.au \
--cc=fio@vger.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