A bug in exported symbols map file

[Valery Kartel]

Hi,

I found a typo in src/libtirpc.map

There is a key_secret_is_set but must be key_secretkey_is_set

So for now key_secretkey_is_set is not exported.

--patch--

--- a/src/libtirpc.map
+++ b/src/libtirpc.map
@@ -298,7 +298,7 @@
     key_gendes;
     key_get_conv;
     key_setsecret;

-    key_secret_is_set;
+    key_secretkey_is_set;
     key_setnet;
     netname2host;
     netname2user;

[Lindsay Walton]

[debbierodgers]

You've identified a typo in the src/libtirpc.map file:

Original entry: key_secret_is_set;
Corrected entry: key_secretkey_is_set;

The typo is that key_secret_is_set should actually be key_secretkey_is_set.
Solution Steps

Identify the Patch
You've provided a patch that shows the necessary change in the src/libtirpc.map file. Let's break down the patch:

diff

--- a/src/libtirpc.map
+++ b/src/libtirpc.map
@@ -298,7 +298,7 @@
key_gendes;
key_get_conv;
key_setsecret;

• key_secret_is_set;

• key_secretkey_is_set;
  key_setnet;
  netname2host;
  netname2user;

  --- a/src/libtirpc.map indicates the original file (a/src/libtirpc.map).
  +++ b/src/libtirpc.map indicates the updated file (b/src/libtirpc.map).
  @@ -298,7 +298,7 @@ specifies the line number where changes begin.
  key_secret_is_set; is the original entry to be replaced.
  key_secretkey_is_set; is the corrected entry.

Explanation of Changes

The line - key_secret_is_set; indicates the removal of key_secret_is_set.
The line + key_secretkey_is_set; indicates the addition of key_secretkey_is_set.

Impact of the Change
By correcting key_secret_is_set to key_secretkey_is_set, you ensure that the correct symbol is exported.
This correction aligns with the intended functionality or naming convention in your project.

[Finle]

Helpful thread issues with libtirpc can get tricky, especially when dealing with legacy systems. Appreciate the insights shared here. Also, for anyone in Pakistan needing to check their
BISP PMT Score this link might help