From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <mhall@mhcomputing.net>
Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170])
 by dpdk.org (Postfix) with ESMTP id 1DE2F47D1
 for <users@dpdk.org>; Sat, 19 Mar 2016 03:45:24 +0100 (CET)
Received: by mail.mhcomputing.net (Postfix, from userid 1000)
 id 99BCF26C; Fri, 18 Mar 2016 19:45:23 -0700 (PDT)
Date: Fri, 18 Mar 2016 19:45:23 -0700
From: Matthew Hall <mhall@mhcomputing.net>
To: Cliff Burdick <shaklee3@gmail.com>
Cc: users@dpdk.org
Message-ID: <20160319024523.GA24378@mhcomputing.net>
References: <CA+Gp1nbABoY7NZ0GXx1Co0cFqUk-1OMKB9T1T2z1JA7QCLnTaQ@mail.gmail.com>
 <20160318215602.GC23135@mhcomputing.net>
 <CA+Gp1naGH4dTm6vkYhu8tXALi9VbHY1xZtrX5EwEzvR3h2g=UQ@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+Gp1naGH4dTm6vkYhu8tXALi9VbHY1xZtrX5EwEzvR3h2g=UQ@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [dpdk-users] Difficulty With rte_eal_init()
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Mar 2016 02:45:24 -0000

On Fri, Mar 18, 2016 at 04:40:28PM -0700, Cliff Burdick wrote:
> In regards to your fix above, how does this change the probing behavior? It
> seems that it's just combining all the .a files into a single library,
> right?

Without these link flags, the constructor functions, which cause ethdev 
drivers to register themselves as probe-able via PCI, do not get invoked 
during library load-time, and the probing always screws up, finding zero 
working Ethernet ports.

> I still needed to include that whole lost if -D options that the
> examples use, or it still didn't seem to probe the bus. I must be missing
> something else as well.

If you have to pass all these -DRTE_MACHINE_* it is most frequently caused by 
an outdated C / C++ compiler. The most recent report of it, which I witnessed, 
then saw reported by a second party on the DPDK mailing list, was caused by a 
branch of clang which was too old to enable the correct accelerations for 
the Haswell, Broadwell, and Skylake series.

The other thing could be you didn't pull in the rte_config.h using -include 
$(RTE_INCLUDE)/rte_config.h and -isystem$(RTE_INCLUDE).

Matthew.