From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2FB87A09E4; Fri, 29 Jan 2021 11:08:07 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1103624016B; Fri, 29 Jan 2021 11:08:07 +0100 (CET) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id C8CC8240134 for ; Fri, 29 Jan 2021 11:08:05 +0100 (CET) IronPort-SDR: 4A/k5UVeJMKbksjjCFItVablW3XOlnHdKl7LBtb81/IKLMl8vOHOLK+E/vETyEkGDpn//r1Dk+ HtfN7c/d05Mg== X-IronPort-AV: E=McAfee;i="6000,8403,9878"; a="177835157" X-IronPort-AV: E=Sophos;i="5.79,385,1602572400"; d="scan'208";a="177835157" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 29 Jan 2021 02:08:03 -0800 IronPort-SDR: qy9SSvq1DH8kaham0DLHNZiodiWlBqFRQV9qQOlvfNsqEDGOtqVBQ+SpzByCgXs/eAGiUkmxGW 1CJ8unkZaigA== X-IronPort-AV: E=Sophos;i="5.79,385,1602572400"; d="scan'208";a="474469993" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.20.59]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA; 29 Jan 2021 02:08:03 -0800 Date: Fri, 29 Jan 2021 10:08:00 +0000 From: Bruce Richardson To: Truring Team Cc: dev@dpdk.org Message-ID: <20210129100800.GC929@bricha3-MOBL.ger.corp.intel.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [dpdk-dev] How to Enable Mellanox Driver Compilation with DPDK20.11 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Jan 29, 2021 at 11:50:08AM +0530, Truring Team wrote: > Hi Team , > > Can someone help me to figure out how to enable the Mellanox Driver flag > in meson.build file , so that dpdk 20.11 compiles with mlx driver enabled. > If the driver is not being built there should be a reason given in the build configuration summary when you run meson. This is almost certainly that you are missing a library dependency for it, since all drivers are enabled unless their dependencies are missing. /Bruce