GCC: Compiling with both static and shared libraries

I apologize if this has been asked before; I searched the forum and didn't find anything.

Is it possible to compile and link a program using GCC such that some of the libraries are linked in as static libraries while the rest are shared?

For example, I have a program, foo, that uses the socket and nsl libraries, but also uses a custom library that won't be available on all systems. I want to link libsocket and libnsl as shared libraries, but the custom one as static.

Can this be done? If so, what is the command line option in GCC for doing so? Thanks in advance.

Just add the static version of the custom library on the command-line of the linking stage of your build.

--
Mats

Odd. I tried that, but linking it the .a file produces a bunch of undefined symbol errors. Linking in the .so works fine, but isn't that still dynamic linking at that point?

Quote:

---

Originally Posted by eatwithaspork

Odd. I tried that, but linking it the .a file produces a bunch of undefined symbol errors. Linking in the .so works fine, but isn't that still dynamic linking at that point?

---

'tis. Strange. Which library do those references the .a "needs" belong to?

--
Mats

Found the problem. The library I'm trying to link statically is libtiff. I didn't phase me that libtiff could have a bunch of its own dependencies, which it does.

Guess it's time to track those down and compile them as well. Thanks for your help.