Home/ Questions/Q 725119
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-14T06:18:04+00:00

Under gcc (g++), I have compiled a static .a (call it some_static_lib.a ) library.

  • 0

Under gcc (g++), I have compiled a static .a (call it some_static_lib.a) library. I want to link (is that the right phrase?) this .a file into another dynamic library (call it libsomeDyn.so) that I’m building. Though the .so compiles, I don’t see content of .a under .so using nm command:

/usr/bin/g++ -fPIC -g -O2 -Wall -Werror -pipe -march=pentium3
-mtune=prescott -MD -D_FILE_OFFSET_BITS=64 -DLINUX -D_GNU_SOURCE -D_THREAD_SAFE -I../../../../../../../../ -I../../../../../../../..//libraries -Wl,-rpath,/usr/lib -o libsomeDyn.so some.o another.o some_static_lib.a -shared -Wl -x
-Wl,-soname,libsomeDyn.so

I do not see functions under some_static_lib.a under libsomeDyn.so. What am I doing wrong?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Static libraries have special rules when it comes to linking. An object from the static library will only be added to the binary if the object provides an unresolved symbol.

    On Linux, you can change that behavior with the --whole-archive linker option:

    g++ -Wl,--whole-archive some_static_lib.a -Wl,--no-whole-archive
    • 0