On Tue, 2 Nov 2004, Bill Moseley wrote:
On Tue, Nov 02, 2004 at 08:35:27AM -0600, Bob Friesenhahn wrote:The main purpose of building a completely static program is to satisfy security or system bootstrap requirements (/usr partition not mounted). It is not always possible to build a completely static program. It is not usually desirable to build a completely static program. Completely static programs don't necessarily work properly when copied to a somewhat different processor type with the same OS, or a different kernel version.
My situation was someone wanted to use the program on their ISP that didn't allow shell access -- but they could ftp a program to their account. So they wanted to build statically and not depend on their ISPs libraries at all.
Right, however, it seems that the user really wants a program which uses the operating system shared libraries (e.g. libc) but links to non-standard libraries statically.
Many years ago (e.g. in old SunOS 4.X.X) statically-linked binaries were more "portable" but since then it has become more portable to dynamically link with the core OS libraries.
Bob ====================================== Bob Friesenhahn bfriesen@xxxxxxxxxxxxxxxxxxx http://www.simplesystems.org/users/bfriesen
_______________________________________________ Autoconf mailing list Autoconf@xxxxxxx http://lists.gnu.org/mailman/listinfo/autoconf
