From owner-freebsd-current  Sun Jan 19 23:26:08 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id XAA16383
          for current-outgoing; Sun, 19 Jan 1997 23:26:08 -0800 (PST)
Received: from time.cdrom.com (time.cdrom.com [204.216.27.226])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA16370;
          Sun, 19 Jan 1997 23:25:43 -0800 (PST)
Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id XAA17489; Sun, 19 Jan 1997 23:25:14 -0800 (PST)
To: John Polstra <jdp@polstra.com>
cc: Mark Murray <mark@grondar.za>, peter@FreeBSD.ORG, current@FreeBSD.ORG
Subject: Re: Static binaries and dlopen(3) with a new crypt(3) lib. 
In-reply-to: Your message of "Sun, 19 Jan 1997 21:34:46 PST."
             <199701200534.VAA25350@austin.polstra.com> 
Date: Sun, 19 Jan 1997 23:25:14 -0800
Message-ID: <17486.853745114@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> I also want to move the dl* functions out of crt0.o, where they
> pollute the namespace and cannot be overridden by user functions
> of the same name.  From a brief look, I don't see any reason that
> they can't be moved into libc.  They do need a tie-in to crt0.o,
> but they don't have to be defined there.  I mention this because
> I wouldn't want to add any new global functions to crt0, but I
> wouldn't feel so bad about adding them to libc, where they can be
> overridden.

I agree.

					Jordan