From owner-freebsd-current  Tue Jan 21 12:19:11 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id MAA10045
          for current-outgoing; Tue, 21 Jan 1997 12:19:11 -0800 (PST)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id MAA10024;
          Tue, 21 Jan 1997 12:18:56 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA19848; Tue, 21 Jan 1997 13:02:01 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199701212002.NAA19848@phaeton.artisoft.com>
Subject: Re: Static binaries and dlopen(3) with a new crypt(3) lib.
To: mark@grondar.za (Mark Murray)
Date: Tue, 21 Jan 1997 13:02:01 -0700 (MST)
Cc: terry@lambert.org, mark@grondar.za, chuckr@glue.umd.edu, jdp@polstra.com,
        peter@FreeBSD.ORG, current@FreeBSD.ORG
In-Reply-To: <199701210603.IAA22421@grackle.grondar.za> from "Mark Murray" at Jan 21, 97 08:03:21 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> What's wrong with the simpler dlopen(3) interface that jdp has offered
> to fix?

There's still a distinction drawn between statically and dynamically
linked binary startup code.  Not a big deal, I suppose; we've lived
with it for several years, now.


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.