From owner-freebsd-hackers  Sat Jan  6 16:21:00 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA01438
          for hackers-outgoing; Sat, 6 Jan 1996 16:21:00 -0800 (PST)
Received: from cs.few.eur.nl (pk@kaa.cs.few.eur.nl [130.115.131.11])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA01433
          for <hackers@FreeBSD.ORG>; Sat, 6 Jan 1996 16:20:57 -0800 (PST)
Received: by cs.few.eur.nl (5.67/EUR)
	id AA14457; Sun, 7 Jan 96 01:19:54 +0100
From: Paul Kranenburg <pk@cs.few.eur.nl>
Message-Id: <9601070019.AA14457@cs.few.eur.nl>
Subject: Re: Anyone got GNU `dld' ported to FreeBSD?
To: dfr@render.com (Doug Rabson)
Date: Sun, 7 Jan 1996 01:19:53 +0100 (MET)
Cc: jdp@polstra.com, hackers@FreeBSD.ORG
In-Reply-To: <Pine.BSF.3.91.960106115114.482D-100000@minnow.render.com> from "Doug Rabson" at Jan 6, 96 11:53:27 am
X-Mailer: ELM [version 2.4 PL13]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> It would be pretty easy in a static binary to 'demand load' ld.so the 
> first time a dl*() function was used, I think.

While this is possible with some niggling work, you might be in for a few
surprises, unless the objects you intend to dlopen() are completely
self-contained. Normally an object is likely to depend on libc so you'd
have to auto-load the shared libc version leaving multiple copies of 
assorted libc routines in your program. Depending on what those routines
are, this might lead to confusing results.

-pk