From owner-freebsd-current Tue Sep 1 18:26:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07154 for freebsd-current-outgoing; Tue, 1 Sep 1998 18:26:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07133 for ; Tue, 1 Sep 1998 18:26:25 -0700 (PDT) (envelope-from jdp@austin.polstra.com) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.8.8/8.8.8) with ESMTP id SAA16732; Tue, 1 Sep 1998 18:25:20 -0700 (PDT) (envelope-from jdp) Message-Id: <199809020125.SAA16732@austin.polstra.com> To: chuckr@glue.umd.edu Subject: Re: E-day problems: rtld-elf dlsym() broken? In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Date: Tue, 01 Sep 1998 18:25:20 -0700 From: John Polstra Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Chuck Robey wrote: > Another tought occurred, tho: Will those functions finally be > available for statically linked elf images? No. Never. I wish you folks would get that idea out of your heads, because it ain't gonna happen. It is not feasible, for reasons having to do with the fact that some variables would end up existing in two places, one in the original static executable and another in whatever object you just dlopened. There are good reasons why these functions have never been supported (by any vendor) in static executables. -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message