From: "Kadam, Pallavi" <pallavi.kadam@intel.com>
To: Tal Shnaiderman <talshn@nvidia.com>, <dev@dpdk.org>
Cc: <thomas@monjalon.net>, <dmitry.kozliuk@gmail.com>,
<navasile@linux.microsoft.com>, <dmitrym@microsoft.com>,
<gakhil@marvell.com>, <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH 2/2] security: build on Windows
Date: Wed, 29 Sep 2021 12:55:18 -0700 [thread overview]
Message-ID: <7dae292c-f431-1fea-ce6f-9d1a83c05d2e@intel.com> (raw)
In-Reply-To: <20210915162603.16652-2-talshn@nvidia.com>
On 9/15/2021 9:26 AM, Tal Shnaiderman wrote:
> Build the security library on Windows.
>
> Remove unneeded export from version file.
>
> Signed-off-by: Tal Shnaiderman <talshn@nvidia.com>
> ---
> Depends-on: patch-98796 ("cryptodev: build on Windows")
> ---
> lib/meson.build | 1 +
> lib/security/version.map | 1 -
> 2 files changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/meson.build b/lib/meson.build
> index 5f3b1cf365..e5f0094a82 100644
> --- a/lib/meson.build
> +++ b/lib/meson.build
> @@ -86,6 +86,7 @@ if is_windows
> 'gso',
> 'latencystats',
> 'pdump',
> + 'security',
> ] # only supported libraries for windows
> endif
>
> diff --git a/lib/security/version.map b/lib/security/version.map
> index c44c7f5f60..6067051552 100644
> --- a/lib/security/version.map
> +++ b/lib/security/version.map
> @@ -1,7 +1,6 @@
> DPDK_22 {
> global:
>
> - rte_security_attach_session;
> rte_security_capabilities_get;
> rte_security_capability_get;
> rte_security_session_create;
Getting linking errors using clang for 'rte_security_get_userdata' and
'rte_security_set_pkt_metadata' as below:
FAILED: lib/rte_security-22.dll
"clang" -Wl,/MACHINE:X64 -Wl,/OUT:lib/rte_security-22.dll
lib/librte_security.a.p/security_rte_security.c.obj "-Wl,/nologo"
"-Wl,/release" "-Wl,/nologo" "-Wl,/OPT:REF" "-Wl,/DLL"
"-Wl,/IMPLIB:lib\rte_security.lib" "lib\rte_eal.lib"
"lib\rte_kvargs.lib" "lib\rte_mempool.lib" "lib\rte_ring.lib"
"lib\rte_cryptodev.lib" "lib\rte_mbuf.lib" "lib\rte_rcu.lib"
"lib\rte_net.lib"
"-Wl,/def:C:\dpdk\ixgbe\dpdk\build\lib\rte_security_exports.def"
"-ldbghelp" "-lsetupapi" "-lws2_32" "-lmincore" "-lkernel32" "-luser32"
"-lgdi32" "-lwinspool" "-lshell32" "-lole32" "-loleaut32" "-luuid"
"-lcomdlg32" "-ladvapi32"
rte_security_exports.def : error LNK2001: unresolved external symbol
rte_security_get_userdata
rte_security_exports.def : error LNK2001: unresolved external symbol
rte_security_set_pkt_metadata
lib\rte_security.lib : fatal error LNK1120: 2 unresolved externals
clang: error: linker command failed with exit code 1120 (use -v to see
invocation)
Should it be removed from version file?
next prev parent reply other threads:[~2021-09-29 19:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 16:26 [dpdk-dev] [PATCH 1/2] security: use the net library for IP structs Tal Shnaiderman
2021-09-15 16:26 ` [dpdk-dev] [PATCH 2/2] security: build on Windows Tal Shnaiderman
2021-09-19 14:07 ` William Tu
2021-09-29 19:55 ` Kadam, Pallavi [this message]
2021-09-30 6:33 ` Tal Shnaiderman
2021-10-01 13:44 ` William Tu
2021-09-15 18:28 ` [dpdk-dev] [EXT] [PATCH 1/2] security: use the net library for IP structs Akhil Goyal
2021-09-16 18:40 ` Tal Shnaiderman
2021-09-19 14:06 ` [dpdk-dev] " 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=7dae292c-f431-1fea-ce6f-9d1a83c05d2e@intel.com \
--to=pallavi.kadam@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=gakhil@marvell.com \
--cc=navasile@linux.microsoft.com \
--cc=talshn@nvidia.com \
--cc=thomas@monjalon.net \
/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).