From: William Tu <u9012063@gmail.com>
To: dpdk-dev <dev@dpdk.org>, Dmitry Kozliuk <dmitry.kozliuk@gmail.com>
Cc: Sergey Madaminov <sergey.madaminov@gmail.com>
Subject: [dpdk-dev] Linker error on rte_dump_stack() on Windows
Date: Sun, 8 Aug 2021 10:45:40 -0700 [thread overview]
Message-ID: <CALDO+SYOWByMKiC5YuPg53XLyBYvs_KffvzjZB59-1qCQKZKqQ@mail.gmail.com> (raw)
Hi,
While linking OVS to Windows DPDK library, static link to
librte_eal.a, we hit some error about rte_dump_stack().
I don't know why other symbols work, but only a couple symbols showed
errors here.
Any suggestions about how to debug/fix this? Thank you!
[5/15] Linking target utilities/ovs-vsctl.exeFAILED:
utilities/ovs-vsctl.exe"clang" -Wl,/MACHINE:X64
-Wl,/OUT:utilities/ovs-vsctl.exe
utilities/ovs-vsctl.exe.p/ovs-vsctl.c.obj "-Wl,/nologo" "-Wl,/release"
"-Wl,/nologo" "-Wl,/OPT:REF" "lib\libopenvswitch.a"
"-Wl,--no-undefined" "C:/dpdk/install/lib/librte_eal.a"
"C:/dpdk/install/lib/librte_ethdev.a"
"C:/dpdk/install/lib/librte_mempool.a"
"C:/dpdk/install/lib/librte_mbuf.a"
"C:/dpdk/install/lib/librte_meter.a""C:/dpdk/install/lib/librte_telemetry.a"
"C:/dpdk/install/lib/librte_kvargs.a"
"C:/PTHREADS-BUILT/lib/libpthreadVC3.lib" "-lWs2_32" "-lWbemUuid"
"-lShlwapi" "-lIphlpapi" "-Wl,/SUBSYSTEM:CONSOLE" "-lkernel32"
"-luser32" "-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32"
"-luuid" "-lcomdlg32" "-ladvapi32"
LINK : warning LNK4044: unrecognized option '/-no-undefined'; ignored
librte_eal.a(eal_windows_eal_debug.c.obj) : error LNK2019: unresolved
external symbol __imp_SymInitialize referenced in function
rte_dump_stack
librte_eal.a(eal_windows_eal_debug.c.obj) : error LNK2019: unresolved
external symbol __imp_SymSetOptions referenced in function
rte_dump_stack
librte_eal.a(eal_windows_eal_debug.c.obj) : error LNK2019: unresolved
external symbol __imp_SymFromAddr referenced in function
rte_dump_stack
librte_eal.a(eal_windows_eal_debug.c.obj) : error LNK2019: unresolved
external symbol __imp_SymGetLineFromAddr64 referenced in function
rte_dump_stack
librte_eal.a(eal_windows_eal_debug.c.obj) : error LNK2019: unresolved
external symbol __imp_SymCleanup referenced in function rte_dump_stack
librte_eal.a(eal_windows_eal_memory.c.obj) : error LNK2019: unresolved
external symbol __imp_SetupDiGetClassDevsA referenced in function
eal_mem_virt2iova_init
Running dumpbin, I can see the rte_dump_stack symbol.
c:\dpdk\install\lib>dumpbin /ALL librte_eal.a | grep rte_dump_stack
D9E52 rte_dump_stack
00000045 REL32 00000000 139 rte_dump_stack
139 00000000 UNDEF notype External | rte_dump_stack
00000000 ADDR32NB 00000000 145 rte_dump_stack
00000004 ADDR32NB 00000239 145 rte_dump_stack
145 00000000 SECT1 notype () External | rte_dump_stack
other symbols look similar...
c:\dpdk\install\lib>dumpbin /ALL librte_eal.a | grep rte_eal_cleanup
CE92C rte_eal_cleanup
00000099 REL32 00000000 13C rte_eal_cleanup
13C 00000000 UNDEF notype External | rte_eal_cleanup
0000000C ADDR32NB 00000000 1B6 rte_eal_cleanup
00000010 ADDR32NB 00000027 1B6 rte_eal_cleanup
1B6 00000100 SECT1 notype () External | rte_eal_cleanup
Thank you
William
next reply other threads:[~2021-08-08 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-08 17:45 William Tu [this message]
2021-08-08 19:52 ` Dmitry Kozlyuk
2021-08-09 2:30 ` 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=CALDO+SYOWByMKiC5YuPg53XLyBYvs_KffvzjZB59-1qCQKZKqQ@mail.gmail.com \
--to=u9012063@gmail.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=sergey.madaminov@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).