From owner-freebsd-current Tue Apr 4 09:04:57 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA14783 for current-outgoing; Tue, 4 Apr 1995 09:04:57 -0700 Received: from trout.sri.MT.net (trout.sri.MT.net [204.182.243.12]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA14769; Tue, 4 Apr 1995 09:03:29 -0700 Received: (from nate@localhost) by trout.sri.MT.net (8.6.9/8.6.9) id KAA06084; Tue, 4 Apr 1995 10:07:09 -0600 Date: Tue, 4 Apr 1995 10:07:09 -0600 From: Nate Williams Message-Id: <199504041607.KAA06084@trout.sri.MT.net> In-Reply-To: "William A. Arbaugh" "Re: READ BEFORE SUPPING: critical change to login/su" (Apr 4, 11:20am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: "William A. Arbaugh" , Paul Traina Subject: Re: READ BEFORE SUPPING: critical change to login/su Cc: current@FreeBSD.org, cvs-committers@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > > Apparently, the linker does not resolve undefined symbols of shared libraries > > at link time, and libskey.so.2.0 makes references to stuff found in libmd.a. > > The modules in libmd.a that skey requires were not getting linked into the > > actual programs that used skey, so when someone actually invoked skey based > > programs like keyinit(1) there were unresolved runtime references > > (bloody amazing this wasn't caught earlier). The reason it wasn't caught earlier is because the linker depended on certain characteristics of linking which I changed. > Shouldn't the linker be fixed to handle the unresolved symbols from a > shared library. Yes. > I agree that skey shouldn't be a shared library, but > that really isn't fixing the real problem though. Someone may stumble > onto this again with another program that uses a mix of shared and static > libraries. I am planning on fixing this, but the whole shared lib/linker code is very new to me. If anyone feels like jumping in feel free to do so since my time is limited due to work commitments. (though sleep will become less important as the release date looms closer). Having two sets of eyes looking through the code certainly can't hurt. Nate