Re: statically linked GTK+ & glibc libraries

[Mark Leisher <mleisher crl nmsu edu>]

    John> Hi Daniel, take a look at the Makefile generated by automake for
    John> your project.  Look for LDADD and check the libraries you are
    John> linking against. Every time you see a library which might cause a
    John> problem (eg. libtiff, libgtk, etc.), wrap a "-Wl,-Bstatic" /
    John> "-Wl,-Bdynamic" pair around it.

As distributions and philosophies diverge over time, eventually you may be
forced to statically link all the libraries.  It happens all the time.  Such
as dealing with multiple generations of commercial Unices your customers use.
This is a good thing.

First, the program is more likely to run on other distros.  Second, you get a
chance to see how bloated libraries and your code have become over the past
few years when the static binary doesn't fit on a CDROM :-)
-----------------------------------------------------------------------------
Mark Leisher                           Sentiment without action
Computing Research Lab                 is the ruin of the soul.
New Mexico State University               -- Edward Abbey
Box 30001, Dept. 3CRL
Las Cruces, NM  88003