Date: Mon, 20 Jan 1997 17:29:16 -0500 (EST) From: Chuck Robey <chuckr@glue.umd.edu> To: Terry Lambert <terry@lambert.org> Cc: jdp@polstra.com, mark@grondar.za, peter@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Static binaries and dlopen(3) with a new crypt(3) lib. Message-ID: <Pine.OSF.3.95.970120172650.2081A-100000@ginger.eng.umd.edu> In-Reply-To: <199701202055.NAA16242@phaeton.artisoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 20 Jan 1997, Terry Lambert wrote: > > The main idea of statically linked stuff is to allow it to work in the > > absence of /usr. This sounds like it's getting close to breaking that, > > no? > > No. If the symbols are only resolved on reference, then they can be > present and unresolved without impacting operation. If a reference > occurs to the symbol and the backing page is not mapped because the > object was not there, *then* a failure can occur. > > How well does dlopen() work in static binaries now? ...not at all. I didn't ask how well dynamic linking works for statically linked apps, my only interest is in maintaining safety for critical things, needed when my system puts it's legs in the air and gasps. Even for dynamic linking, don't break that! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+-----------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.95.970120172650.2081A-100000>