patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Fady Bader <>
Subject: [dpdk-stable] [PATCH] meter: remove inline functions from export list
Date: Wed, 17 Jun 2020 11:15:07 +0300	[thread overview]
Message-ID: <> (raw)

The code didn't compile when using exported meter functions under windows.

error LNK2001: unresolved external symbol rte_meter_srtcm_color_aware_check
error LNK2001: unresolved external symbol rte_meter_srtcm_color_blind_check
error LNK2001: unresolved external symbol rte_meter_trtcm_color_aware_check
error LNK2001: unresolved external symbol rte_meter_trtcm_color_blind_check
error LNK2001: unresolved external symbol
error LNK2001: unresolved external symbol

The cause was that there were some inline functions that were included in the
export list.
To solve this the functions were removed from export list
which are implemented in the header and shouldn't be exported.

Fixes: 655796d2b5fb3d44166e172 ("meter: support RFC4115 trTCM")
Fixes: 9d41beed24b01666913de30 ("lib: provide initial versioning")

Signed-off-by: Fady Bader <>
 lib/librte_meter/ | 6 ------
 1 file changed, 6 deletions(-)

diff --git a/lib/librte_meter/ b/lib/librte_meter/
index b493bcebe9..58859d4d76 100644
--- a/lib/librte_meter/
+++ b/lib/librte_meter/
@@ -1,12 +1,8 @@
 DPDK_20.0 {
-	rte_meter_srtcm_color_aware_check;
-	rte_meter_srtcm_color_blind_check;
-	rte_meter_trtcm_color_aware_check;
-	rte_meter_trtcm_color_blind_check;
@@ -16,8 +12,6 @@ DPDK_20.0 {
 DPDK_21 {
-	rte_meter_trtcm_rfc4115_color_aware_check;
-	rte_meter_trtcm_rfc4115_color_blind_check;

             reply	other threads:[~2020-06-17  8:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-17  8:15 Fady Bader [this message]
2020-06-17  8:24 ` [dpdk-stable] [PATCH v2] " Fady Bader
2020-06-23 17:36   ` Thomas Monjalon

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:

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

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).