From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] mk: get correct clang version
Date: Mon, 25 Jul 2016 17:48:52 +0200 [thread overview]
Message-ID: <2933795.xdyfO1uDcb@xps13> (raw)
In-Reply-To: <20160725152108.GA33408@bricha3-MOBL3>
2016-07-25 16:21, Bruce Richardson:
> On Mon, Jul 25, 2016 at 01:55:48PM +0100, Ferruh Yigit wrote:
> > -dumpversion is for gcc compatibility and doesn't return actual clang
> > version. -dumpversion only returns 4.2.1 for a long time.
> >
> > Fixes: 2ef6eea891e5 ("mk: add clang toolchain")
> >
> > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>
> Confirm this set fixes the issues with shared lib compile on FreeBSD.
>
> Tested-by: Bruce Richardson <bruce.richardson@intel.com>
Applied, thanks
prev parent reply other threads:[~2016-07-25 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 12:55 Ferruh Yigit
2016-07-25 12:55 ` [dpdk-dev] [PATCH 2/2] mk: fix FreeBSD clang compile error Ferruh Yigit
2016-07-25 15:21 ` [dpdk-dev] [PATCH 1/2] mk: get correct clang version Bruce Richardson
2016-07-25 15:48 ` Thomas Monjalon [this message]
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=2933795.xdyfO1uDcb@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).