From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 5/6] mk: add toolchain for clang and linuxapp target
Date: Thu, 17 Jul 2014 17:54:52 +0000 [thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B0343AFE87@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <1571068.2IbkGfH4jp@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, July 17, 2014 3:23 AM
> To: Richardson, Bruce
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 5/6] mk: add toolchain for clang and linuxapp
> target
>
> 2014-07-08 00:36, Bruce Richardson:
> > --- /dev/null
> > +++ b/mk/toolchain/clang/rte.vars.mk
> [...]
> > +ifeq ($(KERNELRELEASE),)
> > +CC = $(CROSS)clang
> > +else
> > +CC = $(CROSS)gcc
> > +endif
>
> Why not use clang for FreeBSD modules?
> This page seems to encourage clang:
> https://wiki.freebsd.org/BuildingFreeBSDWithClang
>
> --
That is an interesting one.
That branch is only really applicable for Linux. In the BSD modules makefile we explicitly unexport CC to allow the build system to use its own default. BSD 9 defaults to using gcc 4.2, and BSD 10 to clang, so this is probably the best approach, leaving the result in the hands of the user. Obviously this won't work with cross-compiling to BSD, but I don't think that is a scenario we support right now anyway.
/Bruce
next prev parent reply other threads:[~2014-07-17 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 23:36 [dpdk-dev] [PATCH 0/6] Clang compilation support on FreeBSD and Linux Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 1/6] pmd_bond: add missing variable initialization Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 2/6] Makefiles: add clang to compiler if/else block Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 3/6] mk: Ensure correct detection of SSE4.2 on FreeBSD Bruce Richardson
2014-07-17 9:35 ` Thomas Monjalon
2014-07-17 21:42 ` Bruce Richardson
2014-07-17 10:25 ` Thomas Monjalon
2014-07-17 14:41 ` Richardson, Bruce
2014-07-17 21:47 ` [dpdk-dev] [PATCH v2 " Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 4/6] acl: add nmmintrin.h header to allow clang compilation Bruce Richardson
2014-07-07 23:36 ` [dpdk-dev] [PATCH 5/6] mk: add toolchain for clang and linuxapp target Bruce Richardson
2014-07-17 10:23 ` Thomas Monjalon
2014-07-17 17:54 ` Richardson, Bruce [this message]
2014-07-07 23:36 ` [dpdk-dev] [PATCH 6/6] config: add compile target for clang on BSD Bruce Richardson
2014-07-11 5:31 ` [dpdk-dev] [PATCH 0/6] Clang compilation support on FreeBSD and Linux Zhan, Zhaochen
2014-07-18 23:58 ` Thomas Monjalon
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=59AF69C657FD0841A61C55336867B5B0343AFE87@IRSMSX103.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).