From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Marc <marcdevel@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] x86_64-native-linuxapp-clang compilation broken?
Date: Mon, 15 Feb 2016 09:39:27 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE202454732@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAExC=0ToFXw7p33QcUGOpezo=K=B=foHxsd2CuXxLBWXASxMGA@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marc
> Sent: Sunday, February 14, 2016 10:21 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] x86_64-native-linuxapp-clang compilation broken?
>
> It seems compilation for clang Linux target is broken:
>
> In file included from
> /home/marc/dpdk/lib/librte_eal/linuxapp/eal/eal_pci.c:42:
> /home/marc/dpdk/x86_64-native-linuxapp-clang/include/rte_memcpy.h:870:2:
> error: implicit declaration of function '_mm_alignr_epi8' is invalid in
> C99
> [-Werror,-Wimplicit-function-declaration]
> MOVEUNALIGNED_LEFT47(dst, src, n, srcofs);
> ^
> ...
>
> marc@dpdk:~/dpdk$ clang --version
> Debian clang version 3.5.0-10 (tags/RELEASE_350/final) (based on LLVM
> 3.5.0)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
Hi,
It compiles ok for me with the latest HEAD and clang 3.70:
$ make install -j T=x86_64-native-linuxapp-clang CC=/usr/bin/clang
...
Build complete [x86_64-native-linuxapp-clang]
...
$ clang --version
clang version 3.7.0 (tags/RELEASE_370/final)
Target: x86_64-redhat-linux-gnu
Thread model: posix
I do have to avoid using the ccached clang since it gives a (different) error about macro expansions. However, that isn't the issue you are seeing.
John
next prev parent reply other threads:[~2016-02-15 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 22:21 Marc
2016-02-15 9:39 ` Mcnamara, John [this message]
2016-02-15 10:14 ` Van Haaren, Harry
2016-02-16 6:08 ` Matthew Hall
2016-02-15 9:44 ` Mcnamara, John
2016-02-16 11:49 ` Mcnamara, John
2016-02-16 12:15 ` Marc
2016-02-16 12:57 ` De Lara Guarch, Pablo
2016-02-16 18:47 ` Matthew Hall
2016-02-16 23:19 ` Marc
2016-02-17 11:07 ` De Lara Guarch, Pablo
2016-02-17 20:23 ` Matthew Hall
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=B27915DBBA3421428155699D51E4CFE202454732@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=dev@dpdk.org \
--cc=marcdevel@gmail.com \
/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).