DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pallavi Kadam <pallavi.kadam@intel.com>
To: William Tu <u9012063@gmail.com>, dev@dpdk.org
Cc: Dmitry Kozliuk <dmitry.kozliuk@gmail.com>
Subject: Re: [dpdk-dev] How to compile and run l2fwd/l3fwd on DPDK windows?
Date: Tue, 4 Feb 2020 13:46:10 -0800	[thread overview]
Message-ID: <c9f704fb-1cc2-60b6-ad5f-6eea45cb7d3e@intel.com> (raw)
In-Reply-To: <CALDO+SauKMJGedA_ZxjF=k8P1D3+st2mzFqw3XDSa6gk9pfuJg@mail.gmail.com>

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 <netinet/in.h>
>           ^~~~~~~~~~~~~~
> 1 error generated.
>
> Thanks for your help
> William

  reply	other threads:[~2020-02-04 21:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 21:25 William Tu
2020-02-04 21:46 ` Pallavi Kadam [this message]
2020-02-04 23:12   ` William Tu
2020-02-04 21:47 ` Thomas Monjalon
2020-02-04 23:11   ` William Tu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c9f704fb-1cc2-60b6-ad5f-6eea45cb7d3e@intel.com \
    --to=pallavi.kadam@intel.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=u9012063@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).