From: David Nellans <david@nellans.org>
To: David N <android.wm.edu@gmail.com>, fio@vger.kernel.org
Subject: Re: fio execution issue on Android device with MediaTek
Date: Thu, 19 Jun 2014 16:04:31 -0500 [thread overview]
Message-ID: <53A3505F.1000809@nellans.org> (raw)
In-Reply-To: <CACTzACWfzQpXwfrBuneYiDFYR=ERUXXaA3oOOz62oEvXa5xNCA@mail.gmail.com>
generally speaking taking a pre-compiled binary from one machine to
another is a dicey proposition
but in this case you're moving from a krait 400? which runs armv7 to the
MT6572 which is a cortex A-7
which are the same ISA rev. are you running the exact same distro
and/or set of libs on them too?
changes there in glibc, will cause issues. cross compiling for x86
certainly isn't going to fix your problems!
just for good measure I did just compile and run fio tip on a tegra k1
running ubuntu 13.04 (3.10.33 kern)
and it seems to be working just fine. have you managed to get anything
at all to work via this method?
i doubt its an issue specific to fio.
- the real David N
On 06/19/2014 03:39 PM, David N wrote:
> Hi all,
>
> I got fio working fine on a device with Qualcomm Snapdragon but
> executing that same compiled binary gave me "sh: ./fio: not
> executable: magic 7F45" on a MediaTek (MT6572) device.
>
> I tried to recompile both for ARM and x86 but still the same issue.
> The binary is executable (did chmod it), so I'm not sure what is
> causing this. I'd very much appreciate any input.
>
> Thanks much!
> David
> --
> To unsubscribe from this list: send the line "unsubscribe fio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-06-19 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-19 20:39 fio execution issue on Android device with MediaTek David N
2014-06-19 21:04 ` David Nellans [this message]
2014-06-19 21:13 ` David Nellans
2014-06-19 21:25 ` David N
2014-06-19 21:38 ` David Nellans
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=53A3505F.1000809@nellans.org \
--to=david@nellans.org \
--cc=android.wm.edu@gmail.com \
--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