From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <bruce.richardson@intel.com>
Received: from mga14.intel.com (mga14.intel.com [192.55.52.115])
 by dpdk.org (Postfix) with ESMTP id 7BF3F2C8
 for <dev@dpdk.org>; Tue, 20 Jun 2017 15:41:32 +0200 (CEST)
Received: from orsmga004.jf.intel.com ([10.7.209.38])
 by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384;
 20 Jun 2017 06:41:31 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.39,364,1493708400"; d="scan'208";a="99753656"
Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.28])
 by orsmga004.jf.intel.com with SMTP; 20 Jun 2017 06:41:28 -0700
Received: by  (sSMTP sendmail emulation); Tue, 20 Jun 2017 14:41:27 +0100
Date: Tue, 20 Jun 2017 14:41:27 +0100
From: Bruce Richardson <bruce.richardson@intel.com>
To: Morten =?iso-8859-1?Q?Br=F8rup?= <mb@smartsharesystems.com>
Cc: "Wiles, Keith" <keith.wiles@intel.com>,
 Christian Ehrhardt <christian.ehrhardt@canonical.com>,
 Stephen Hemminger <stephen@networkplumber.org>, dev <dev@dpdk.org>
Message-ID: <20170620134127.GA89552@bricha3-MOBL3.ger.corp.intel.com>
References: <20170607104743.275149-1-bruce.richardson@intel.com>
 <20170607162617.00d009ff@xeon-e3>
 <20170608085901.GC58216@bricha3-MOBL3.ger.corp.intel.com>
 <20170608092658.6a4bfc5c@xeon-e3>
 <CAATJJ0K3Nn0Oo8j+twO6zG5XRtCjRtBWGS1gx_qp2Pu5E7N-kQ@mail.gmail.com>
 <20170609090515.GB59768@bricha3-MOBL3.ger.corp.intel.com>
 <946E12D3-50BD-49DF-A73F-F29896C7DDDD@intel.com>
 <98CBD80474FA8B44BF855DF32C47DC359EB177@smartserver.smartshare.dk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC359EB177@smartserver.smartshare.dk>
Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?=
 =?iso-8859-1?Q?opment?= Ireland Ltd.
User-Agent: Mutt/1.8.1 (2017-04-11)
Subject: Re: [dpdk-dev] [RFC PATCH] replace DPDK config and build system
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Jun 2017 13:41:33 -0000

On Tue, Jun 20, 2017 at 03:34:58PM +0200, Morten Brørup wrote:
> FYI: We are using Crosstool-NG (http://crosstool-ng.github.io/). It seems to be quite popular for cross compiling.
> 

How does a tool like that interact with build-systems then - either with
our current one, or with a hypothetical future one using meson+ninja as
below? Does it simplify what needs to be provided in the build config
tool?

/Bruce

> 
> Med venlig hilsen / kind regards
> - Morten Brørup
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wiles, Keith
> > Sent: Friday, June 9, 2017 8:06 PM
> > To: Richardson, Bruce
> > Cc: Christian Ehrhardt; Stephen Hemminger; dev
> > Subject: Re: [dpdk-dev] [RFC PATCH] replace DPDK config and build
> > system
> > 
> > 
> > > On Jun 9, 2017, at 4:05 AM, Bruce Richardson
> > <bruce.richardson@intel.com> wrote:
> > >
> > > On Thu, Jun 08, 2017 at 12:07:05PM -0600, Christian Ehrhardt wrote:
> > >> On Thu, Jun 8, 2017 at 10:26 AM, Stephen Hemminger <
> > >> stephen@networkplumber.org> wrote:
> > >>
> > >>> On a side note, it would be good to use the GCC extensions that
> > >>> allow building different versions of the same routine into one
> > binary.
> > >>>
> > >>
> > >> And we are back to the discussion we had two years ago about how to
> > >> deliver generic yet also optimized binaries in one shot.
> > >> But if the new build system can enable us to do so I'm all in for
> > that.
> > >>
> > >> Thanks for bringing this up in that context Stephen - might be just
> > >> the right time to look at it again.
> > >>
> > > Yep, we can do that. First though, we need to decide what our minimum
> > > supported compiler baseline is going to be.
> > > Also, if the replace the build system, do we want to do a complete
> > > on-shot replacement, or do we want to keep the older one around in
> > > parallel for a while e.g. to support older OS's and compilers.
> > 
> > I think it would be a good idea to keep the old version for now.
> > 
> > I would suggest adding the new build system to a sandbox repo until we
> > think we have parity then merge into main. Keep the old system in place
> > to allow for other systems until we believe we really have covered all
> > of the bases.
> > 
> > What would your baseline be ?
> > 
> > I would suggest pick a few distros like Linux Ubuntu, Fedora, Red Hat
> > just a guess at the ones we need to support first.
> > 
> > Think we have to support IA and ARM at the same time for the few
> > distros we start with first or at least pick the most used one for ARM
> > first.
> > 
> > >
> > > /Bruce
> > 
> > Regards,
> > Keith
> > 
>