From: Walker, Benjamin <benjamin.walker at intel.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Error while compiling the spdk-16.12 for arm64 architecture
Date: Tue, 28 Feb 2017 16:40:54 +0000 [thread overview]
Message-ID: <1488300053.9792.9.camel@intel.com> (raw)
In-Reply-To: CALTqRrPdwJrMkzS6xPFDCH1DXfj-VUSsopE35yYJ1cRYTNBGmQ@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]
On Tue, 2017-02-28 at 17:48 +0530, Balaji G wrote:
> Hi All,
> I have downloaded the spdk-16.12.zip
> and tried to compile for the arm64 architecture but i got the
> following error
>
> In file included from nvme_ctlr_cmd.c:30:0:
> nvme_internal.h:49:23:fatal error:x86intrin.h: No such file or
> directory
> Compilation terminated.
>
> So, can anyone tell me does the spdk has the support for ARM
> architecture
SPDK only supports x86 and x86-64 today. There isn't anything
particularly tricky about porting to ARM that I can think of off the
top of my head and we'd happily accept patches for the few required
modifications if someone wanted to contribute.
Note that in our current continuous integration set up, there are only
x86-64 systems. If someone wanted to step up and provide proper ARM
support, they'd need to take on the responsibility of testing at least
compilation somehow or it would be likely that the support would
quickly bit rot.
>
>
>
>
> Regards,
> G.Balaji
> _______________________________________________
> SPDK mailing list
> SPDK(a)lists.01.org
> https://lists.01.org/mailman/listinfo/spdk
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3274 bytes --]
next reply other threads:[~2017-02-28 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 16:40 Walker, Benjamin [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-28 17:54 [SPDK] Error while compiling the spdk-16.12 for arm64 architecture Isaac Otsiabah
2017-02-28 12:18 Balaji G
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=1488300053.9792.9.camel@intel.com \
--to=spdk@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.