From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 46AE3A0535; Tue, 4 Feb 2020 22:46:14 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9EB761C1EC; Tue, 4 Feb 2020 22:46:13 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id E325C1C1E6 for ; Tue, 4 Feb 2020 22:46:11 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Feb 2020 13:46:10 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.70,403,1574150400"; d="scan'208,217";a="263996982" Received: from unknown (HELO [10.241.225.141]) ([10.241.225.141]) by fmsmga002.fm.intel.com with ESMTP; 04 Feb 2020 13:46:10 -0800 To: William Tu , dev@dpdk.org Cc: Dmitry Kozliuk References: From: Pallavi Kadam Message-ID: Date: Tue, 4 Feb 2020 13:46:10 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] How to compile and run l2fwd/l3fwd on DPDK windows? 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" Hi William, On 2/4/2020 1:25 PM, William Tu wrote: > Hi, > > I'm able to follow the doc to run helloworld example > https://doc.dpdk.org/guides/windows_gsg/build_dpdk.html#build-the-code > > I'm thinking about running l2fwd on my x710 card. > Is there any step-by-step document to follow? Currently, L2fwd/ L3fwd is WIP and does not have support on dpdk master branch. But, you can refer to draft repository and checkout windpdk-v18.08-clang. This has a Visual Studio solution file and you'll need Clang-llvm and Visual Studio to build the project. You can refer to dpdk-draft-windows\doc\guides\windows.md for more details. However, you can use Clang compiler instead of ICC. We are working on updating the doc to change it to Clang compiler and not ICC. > > So far I'm not able to compile the l3fwd and l2fwd. > meson fails for l3fwd: > c:\dpdk>meson --reconfigure -Dexamples=l3fwd build > The Meson build system > examples\meson.build:93:4: ERROR: Problem encountered: Missing > dependency "hash" for example "l3fwd" > > ninja fails for l2fwd: > c:\dpdk>meson --reconfigure -Dexamples=l2fwd build > c:\dpdk\build>ninja -v > [1/18] "C:/Python38/python.exe" "../buildtools/map_to_def.py" > "C:/dpdk/lib/librte_kvargs/rte_kvargs_version.map" > "lib/rte_kvargs_exports.def" > [2/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_windows_eal_eal_debug.c.obj.rsp > ../lib/librte_eal/windows/eal/eal_debug.c:16:42: warning: format > string is not a string literal [-Wformat-nonliteral] > rte_vlog(RTE_LOG_CRIT, RTE_LOGTYPE_EAL, format, ap); > ^~~~~~ > ../lib/librte_eal/windows/eal/eal_debug.c:10:1: warning: no previous > prototype for function '__rte_panic' [-Wmissing-prototypes] > __rte_panic(const char *funcname, const char *format, ...) > ^ > 2 warnings generated. > [3/18] clang @lib/76b5a35@@rte_kvargs@sta/librte_kvargs_rte_kvargs.c.obj.rsp > [4/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_common_eal_common_lcore.c.obj.rsp > [5/18] llvm-ar "csrD" lib/librte_kvargs.a @lib/librte_kvargs.a.rsp > [6/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_common_eal_common_launch.c.obj.rsp > [7/18] clang @lib/librte_kvargs-0.200.dll.rsp > clang.exe: warning: argument unused during compilation: '-pthread' > [-Wunused-command-line-argument] > LINK : warning LNK4044: unrecognized option '/-no-as-needed'; ignored > Creating library lib\librte_kvargs.dll.a and object lib\librte_kvargs.dll.exp > [8/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_common_eal_common_log.c.obj.rsp > [9/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_common_eal_common_errno.c.obj.rsp > [10/18] "C:\Python38\Scripts\meson" --internal symbolextractor > lib/librte_kvargs-0.200.dll > lib/76b5a35@@rte_kvargs@sha/librte_kvargs-0.200.dll.symbols > [11/18] "C:/Python38/python.exe" "../buildtools/map_to_def.py" > "C:/dpdk/lib/librte_eal/rte_eal_version.map" "lib/rte_eal_exports.def" > [12/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_windows_eal_eal.c.obj.rsp > [13/18] clang @lib/76b5a35@@rte_eal@sta/librte_eal_windows_eal_eal_thread.c.obj.rsp > [14/18] clang @examples/c590b3c@@dpdk-l2fwd@exe/l2fwd_main.c.obj.rsp > FAILED: examples/c590b3c@@dpdk-l2fwd@exe/l2fwd_main.c.obj > clang @examples/c590b3c@@dpdk-l2fwd@exe/l2fwd_main.c.obj.rsp > ../examples/l2fwd/main.c:12:10: fatal error: 'netinet/in.h' file not found > #include > ^~~~~~~~~~~~~~ > 1 error generated. > > Thanks for your help > William