From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] ARM Clang cross-compilation
Date: Thu, 2 Apr 2020 08:05:21 +0000 [thread overview]
Message-ID: <2b9d22ebe1c041788572d0a6e1e57103@pantheon.tech> (raw)
Hi dpdk devs,
Has anyone tried to do an x86 -> aarch64 cross compilation using clang (I'm using an 4.15.0-91-generic Ubuntu 18.04 VM as the build machine)? I've tried a meson build with this cross file:
[binaries]
c = 'clang-9'
cpp = 'clang++-9'
ar = 'llvm-ar-9'
strip = 'llvm-strip-9'
llvm-config = 'llvm-config-9'
pcap-config = ''
[host_machine]
system = 'linux'
cpu_family = 'aarch64'
cpu = 'armv8-a'
endian = 'little'
[properties]
implementor_id = 'generic'
implementor_pn = 'default'
But I'm hitting these errors:
../lib/librte_eal/common/include/arch/arm/rte_pause_64.h:23:15: error: invalid instruction mnemonic 'yield'
asm volatile("yield" ::: "memory");
^
<inline asm>:1:2: note: instantiated into assembly here
yield
^~~~~
Full log here https://pastebin.com/raw/r04MVYti.
Looking at meson docs, I was under the impression that I only needed the right config in the cross-file, but I don't know whether there's a problem with my cross file or there's a problem with the build.
Any help would be appreciated.
Thanks,
Juraj
reply other threads:[~2020-04-02 8:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2b9d22ebe1c041788572d0a6e1e57103@pantheon.tech \
--to=juraj.linkes@pantheon.tech \
--cc=dev@dpdk.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).