From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: pmdinfogen issues: cross compilation for ARM fails
	with older host compiler
Date: Tue, 15 Nov 2016 17:33:04 +0100
Message-ID: <1735931.lIL2RbIZ06@xps13>
References: <DB5PR04MB1605F64CF0D986E0B2B26AF089BB0@DB5PR04MB1605.eurprd04.prod.outlook.com>
 <DB5PR04MB1605203F2297ED88A47270F189BF0@DB5PR04MB1605.eurprd04.prod.outlook.com>
 <20161115142750.GA11283@hmsreliant.think-freely.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Hemant Agrawal <hemant.agrawal@nxp.com>,
 Jerin Jacob <jerin.jacob@caviumnetworks.com>, Jerin.Jacob@cavium.com,
 Jan Viktorin <viktorin@rehivetech.com>
To: Neil Horman <nhorman@tuxdriver.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f47.google.com (mail-wm0-f47.google.com [74.125.82.47])
 by dpdk.org (Postfix) with ESMTP id 17D793977
 for <dev@dpdk.org>; Tue, 15 Nov 2016 17:33:06 +0100 (CET)
Received: by mail-wm0-f47.google.com with SMTP id f82so9991190wmf.1
 for <dev@dpdk.org>; Tue, 15 Nov 2016 08:33:06 -0800 (PST)
In-Reply-To: <20161115142750.GA11283@hmsreliant.think-freely.org>
List-Id: patches and discussions about DPDK <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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2016-11-15 09:27, Neil Horman:
> On Tue, Nov 15, 2016 at 09:34:16AM +0000, Hemant Agrawal wrote:
> > > > On Fri, Nov 11, 2016 at 10:34:39AM +0000, Hemant Agrawal wrote:
> > > > > Hi Neil,
> > > > >    Pmdinfogen compiles with host compiler. It usages rte_byteorder.h
> > > > >    of the target platform.
[...]
> > > Yeah, so what we need is a way to get to the host version of rte_byteorder.h
> > > when building in a cross environment
> > > 
> > +1 
> > 
> Actually, looking at this, I think we're 90% there anyway.  The buildtools
> already uses the hostapp.mk file (as it should), to target the host build
> system, rather than any cross target, so we're good there.  The only question
> is, should we be using rte_byteorder.h at all, and I think the answer is no, we
> shouldn't.  I assert that because the byteorder file is configured for the
> target, not the host, and so we shouldn't be touching it at all.  Instead we
> should just be using the posix htobe*/htole*/letoh*/betoh* variants to do the
> endian conversion, as those are always configured to work on the local build
> host.

Yes there are 2 possible fixes:
- get a host version of EAL
- do not use EAL for host applications

As Neil, I think there is no point in using EAL for a host application.