From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Marc <marcdevel@gmail.com>, "Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] x86_64-native-linuxapp-clang compilation broken?
Date: Tue, 16 Feb 2016 12:57:24 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C8A6204@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAExC=0RU9T6jEDqcNMFvv6o9R70i0bT_ObrRgaghtG5-V5w3ag@mail.gmail.com>
Hi Marc,
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marc
> Sent: Tuesday, February 16, 2016 12:16 PM
> To: Mcnamara, John
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] x86_64-native-linuxapp-clang compilation broken?
>
> On 16 February 2016 at 12:49, Mcnamara, John
> <john.mcnamara@intel.com>
> wrote:
>
> >
> >
> > > -----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:
> > >
> > >...
> > >
> > > 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
> > >
> > > Any ideas?
> >
> > Hi,
> >
> > I built clang 3.5.0 and built DPDK successfully with it on FC23:
> >
> > $ /tmp/llvm-3.5.0.src/Release+Asserts/bin/clang --version
> > clang version 3.5.0 (tags/RELEASE_350/final)
> > Target: x86_64-unknown-linux-gnu
> > Thread model: posix
> >
> > What OS version are you using?
> >
>
> Debian 8, amd64
We suspect this might be an architecture dependent issue.
Could you tell us which CPU you are using?
Thanks,
Pablo
>
> Regards
> Marc
>
>
> >
> > John
> >
> >
next prev parent reply other threads:[~2016-02-16 12:57 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
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 [this message]
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=E115CCD9D858EF4F90C690B0DCB4D8973C8A6204@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--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).