Re: 3.3 configure static

[Andrew Haley <aph at redhat dot com>]

Erik Poupaert writes:
 > > We do this all the time.  The only problem I can think of is that a
 > > really old glibc may not be suitable.
 > 
 > I've now tested (on my own machine) with a dummy user "deploy", with a directory
 > "lib" in his home folder that contains:
 > 
 > Now, for this user, and on my machine, it seems to work. There are
 > no dependencies on /usr/local/gcj/3.3/lib any longer. So I think I
 > can consider such deployment to a "lib" folder feasible on most
 > linux systems, that are sufficiently recent (how recent?), unless
 > I've forgotten something?

Yes.

 > Are there any dependencies in the ldd list that I shouldn't expect to be present on
 > the average linux system, with Gnome and Gtk2 present already?

You need RPM.  RPM allows you to specify up-to-date versions of the
libraries you use, thus avoiding shared library chaos.

That way, if someone installes on a machine with libraries that are
too old, she'll be told what packages to update.

Andrew.