Linux下如何在libgcrypt共享库中添加自定义函数？编译成功但链接报错

Hey there, let's troubleshoot that link-time error you're hitting after customizing libgcrypt. I've messed around with patching crypto libraries like this before, so here are the most common fixes to try:

1. Fix Symbol Visibility (The #1 Culprit) #

libgcrypt uses strict symbol visibility controls to hide internal symbols from the public API. If your custom function isn't marked with the right visibility attribute, it'll be hidden even after compiling, so the linker can't find it.

• How to fix it:
  Add the visibility attribute to both your function prototype (in gcrypt.h) and definition (in visibility.c):

  // In src/gcrypt.h
  __attribute__((visibility("default")))
  void my_custom_gcrypt_function(void);
  
  // In src/visibility.c
  __attribute__((visibility("default")))
  void my_custom_gcrypt_function(void) {
      // Your custom logic here
  }
  

  This tells the compiler to expose this symbol in the shared library's public symbol table.

2. Ensure Your Changes Are Actually Compiled #

Sometimes build systems (like Autotools, which libgcrypt uses) don't pick up new code changes automatically, especially if you modified an existing file without triggering a full rebuild.

• How to fix it:
  1. Run make clean to wipe all old compiled objects
  2. Re-run ./configure to regenerate build scripts (this ensures your header changes are picked up)
  3. Run make to rebuild the entire library
  4. Verify the symbol exists: Use nm -D src/.libs/libgcrypt.so | grep my_custom_gcrypt_function — if you see the symbol listed, it's been compiled into the library.

3. Link Against Your Custom Library (Not the System Default) #

Chances are your test program is linking to the pre-installed system libgcrypt instead of your modified version.

• How to fix it:
  When compiling your test code, explicitly point to your custom library's directory:

  gcc my_test_code.c -o my_test -L./src/.libs -lgcrypt
  

  Before running the test, make sure the dynamic linker uses your library first:

  export LD_LIBRARY_PATH=./src/.libs:$LD_LIBRARY_PATH
  

  Use ldd my_test to confirm — it should show your custom library path, not /usr/lib or similar.

4. Double-Check Function Prototype Consistency #

A mismatch between your header prototype and function definition will cause the linker to throw an "undefined reference" error, even if everything else looks right.

• What to check:
  • Return type (e.g., int vs void)
  • Parameter types (e.g., const char* vs char*)
  • Number of parameters
  • Any const or volatile modifiers
    Make sure both the prototype in gcrypt.h and the implementation in visibility.c are identical.

5. Avoid Over-Stripping or Static Linking #

If you built libgcrypt with static linking enabled or ran strip on the shared library, your custom symbol might have been removed.

• How to fix it:
  • When configuring, use ./configure --disable-static to ensure you're building a dynamic library
  • Skip running strip on the generated .so file, or use strip --strip-unneeded instead (this only removes unused internal symbols, keeping your custom one intact)

内容的提问来源于stack exchange，提问作者bholanath