From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id B668B5B26 for ; Thu, 4 Apr 2019 10:45:29 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2019 01:45:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,306,1549958400"; d="scan'208";a="139902846" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.110.206]) by orsmga003.jf.intel.com with ESMTP; 04 Apr 2019 01:45:25 -0700 Date: Thu, 4 Apr 2019 16:40:31 +0800 From: Ye Xiaolong To: Luca Boccassi Cc: Ferruh Yigit , dev@dpdk.org, Stephen Hemminger , Qi Zhang , Karlsson Magnus , Topel Bjorn , Maxime Coquelin , Bruce Richardson , Ananyev Konstantin , David Marchand , Andrew Rybchenko , Olivier Matz Message-ID: <20190404084030.GA34048@intel.com> References: <20190301080947.91086-1-xiaolong.ye@intel.com> <20190403165949.44857-1-xiaolong.ye@intel.com> <20190403165949.44857-2-xiaolong.ye@intel.com> <25be95ff-132c-9e3e-fe3d-b5aac3dfb388@intel.com> <181fca1e5a2274ad2e7638c25b459ab7f426f254.camel@debian.org> <20190404055515.GB45121@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH v10 1/1] net/af_xdp: introduce AF XDP PMD driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Apr 2019 08:45:30 -0000 On 04/04, Luca Boccassi wrote: >> >> After apply the fix in af_xdp pmd's meson.build, now I was able to >> build >> library for af_xdp pmd. >> >> $ ls drivers/ |grep xdp >> a715181@@rte_pmd_af_xdp@sha >> a715181@@rte_pmd_af_xdp@sta >> a715181@@tmp_rte_pmd_af_xdp@sta >> librte_pmd_af_xdp.a >> librte_pmd_af_xdp.so >> librte_pmd_af_xdp.so.1 >> librte_pmd_af_xdp.so.1.1 >> libtmp_rte_pmd_af_xdp.a >> rte_pmd_af_xdp.pmd.c >> >> But I found that if I install libbpf to /usr/local/lib64 by default, >> application >> built by meson build will fail to run: >> >> $ ./dpdk-testpmd >> ./dpdk-testpmd: error while loading shared libraries: libbpf.so.0: >> cannot open shared object file: No such file or directory >> >> While install libbpf to /usr/lib doesn't have this issue (I was >> testing on ubuntu system). >> Is it a expected behavior? Do we need any fix for it? > >Hi, > >That is expected and distro specific: if your distro doesn't add >/usr/local/lib* to the compiler path, it also won't be in the >LD_LIBRARY_PATH. > >So if you do: > >LD_LIBRARY_PATH=/usr/local/lib64 ./dpdk-testpmd Yes, it does work for me. > >It should then work. It's not related to the build system, but just to >what the default paths are in the distro. Thanks for confirmation, then I can send my v11 out :) Thanks, Xiaolong > >-- >Kind regards, >Luca Boccassi From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 2E629A0679 for ; Thu, 4 Apr 2019 10:45:33 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9A8E55B34; Thu, 4 Apr 2019 10:45:31 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id B668B5B26 for ; Thu, 4 Apr 2019 10:45:29 +0200 (CEST) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Apr 2019 01:45:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,306,1549958400"; d="scan'208";a="139902846" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.110.206]) by orsmga003.jf.intel.com with ESMTP; 04 Apr 2019 01:45:25 -0700 Date: Thu, 4 Apr 2019 16:40:31 +0800 From: Ye Xiaolong To: Luca Boccassi Cc: Ferruh Yigit , dev@dpdk.org, Stephen Hemminger , Qi Zhang , Karlsson Magnus , Topel Bjorn , Maxime Coquelin , Bruce Richardson , Ananyev Konstantin , David Marchand , Andrew Rybchenko , Olivier Matz Message-ID: <20190404084030.GA34048@intel.com> References: <20190301080947.91086-1-xiaolong.ye@intel.com> <20190403165949.44857-1-xiaolong.ye@intel.com> <20190403165949.44857-2-xiaolong.ye@intel.com> <25be95ff-132c-9e3e-fe3d-b5aac3dfb388@intel.com> <181fca1e5a2274ad2e7638c25b459ab7f426f254.camel@debian.org> <20190404055515.GB45121@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH v10 1/1] net/af_xdp: introduce AF XDP PMD driver X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" Message-ID: <20190404084031.lN5JuYs-sW4PA-0pjrpTEyZTHSLK54nsXVXCV6C8PDM@z> On 04/04, Luca Boccassi wrote: >> >> After apply the fix in af_xdp pmd's meson.build, now I was able to >> build >> library for af_xdp pmd. >> >> $ ls drivers/ |grep xdp >> a715181@@rte_pmd_af_xdp@sha >> a715181@@rte_pmd_af_xdp@sta >> a715181@@tmp_rte_pmd_af_xdp@sta >> librte_pmd_af_xdp.a >> librte_pmd_af_xdp.so >> librte_pmd_af_xdp.so.1 >> librte_pmd_af_xdp.so.1.1 >> libtmp_rte_pmd_af_xdp.a >> rte_pmd_af_xdp.pmd.c >> >> But I found that if I install libbpf to /usr/local/lib64 by default, >> application >> built by meson build will fail to run: >> >> $ ./dpdk-testpmd >> ./dpdk-testpmd: error while loading shared libraries: libbpf.so.0: >> cannot open shared object file: No such file or directory >> >> While install libbpf to /usr/lib doesn't have this issue (I was >> testing on ubuntu system). >> Is it a expected behavior? Do we need any fix for it? > >Hi, > >That is expected and distro specific: if your distro doesn't add >/usr/local/lib* to the compiler path, it also won't be in the >LD_LIBRARY_PATH. > >So if you do: > >LD_LIBRARY_PATH=/usr/local/lib64 ./dpdk-testpmd Yes, it does work for me. > >It should then work. It's not related to the build system, but just to >what the default paths are in the distro. Thanks for confirmation, then I can send my v11 out :) Thanks, Xiaolong > >-- >Kind regards, >Luca Boccassi