DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
To: Fady Bader <fady@mellanox.com>
Cc: dev@dpdk.org, thomas@monjalon.net, talshn@mellanox.com,
	yohadt@mellanox.com, olivier.matz@6wind.com,
	harini.ramakrishnan@microsoft.com, ocardona@microsoft.com,
	anand.rawat@intel.com, ranjit.menon@intel.com
Subject: Re: [dpdk-dev] [PATCH] ring: build on Windows
Date: Wed, 20 May 2020 13:08:20 +0300	[thread overview]
Message-ID: <20200520130820.408649f1@sovereign> (raw)
In-Reply-To: <20200520093444.14904-1-fady@mellanox.com>

On Wed, 20 May 2020 12:34:44 +0300
Fady Bader <fady@mellanox.com> wrote:

> Exported per_lcore__rte_errno function to compile ring for windows.
> 
> compilation error logs:
> librte_ring_rte_ring.c.obj : error LNK2019: unresolved
> external symbol per_lcore__rte_errno referenced in
> function rte_ring_lookup
> 
> The cause was that per_lcore__rte_errno function wasn't included
> in the export list.
> To solve this per_lcore__rte_errno was added to the Windows export
> list.
> 
> Signed-off-by: Fady Bader <fady@mellanox.com>
> Depends-on: series-9374 ("Windows basic memory management")
> ---
>  lib/librte_eal/rte_eal_exports.def | 1 +
>  lib/librte_eal/rte_eal_version.map | 5 ++++-
>  lib/meson.build                    | 2 +-
>  3 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/librte_eal/rte_eal_exports.def
> b/lib/librte_eal/rte_eal_exports.def index 854b83bcd..cbb6b8cfe 100644
> --- a/lib/librte_eal/rte_eal_exports.def
> +++ b/lib/librte_eal/rte_eal_exports.def
> @@ -1,5 +1,6 @@
>  EXPORTS
>  	__rte_panic
> +	per_lcore__rte_errno
>  	rte_calloc
>  	rte_calloc_socket
>  	rte_eal_get_configuration
> diff --git a/lib/librte_eal/rte_eal_version.map
> b/lib/librte_eal/rte_eal_version.map index bdd014638..1a1dedcd9 100644
> --- a/lib/librte_eal/rte_eal_version.map
> +++ b/lib/librte_eal/rte_eal_version.map
> @@ -390,4 +390,7 @@ EXPERIMENTAL {
>  	rte_trace_point_lookup;
>  	rte_trace_regexp;
>  	rte_trace_save;
> -};
> +
> +	# added in 20.08
> +	__emutls_v.per_lcore__rte_errno;
> +};
> \ No newline at end of file

No newline at end of file.

> diff --git a/lib/meson.build b/lib/meson.build
> index d190d84ef..5b644f5cd 100644
> --- a/lib/meson.build
> +++ b/lib/meson.build
> @@ -36,7 +36,7 @@ libraries = [
>  	'flow_classify', 'bpf', 'graph', 'node']
>  
>  if is_windows
> -	libraries = ['kvargs','eal'] # only supported libraries for
> windows
> +	libraries = ['kvargs','eal','ring'] # only supported

Please always place spaces after commas. And IMO, it's time to start
breaking this list into lines as the common list above it does.

> libraries for windows endif
>  
>  default_cflags = machine_args

--
Dmitry Kozlyuk

      reply	other threads:[~2020-05-20 10:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20  9:34 Fady Bader
2020-05-20 10:08 ` Dmitry Kozlyuk [this message]

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=20200520130820.408649f1@sovereign \
    --to=dmitry.kozliuk@gmail.com \
    --cc=anand.rawat@intel.com \
    --cc=dev@dpdk.org \
    --cc=fady@mellanox.com \
    --cc=harini.ramakrishnan@microsoft.com \
    --cc=ocardona@microsoft.com \
    --cc=olivier.matz@6wind.com \
    --cc=ranjit.menon@intel.com \
    --cc=talshn@mellanox.com \
    --cc=thomas@monjalon.net \
    --cc=yohadt@mellanox.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).