From owner-freebsd-current Tue Mar 28 10:16:25 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id KAA23021 for current-outgoing; Tue, 28 Mar 1995 10:16:25 -0800 Received: from rocky.sri.MT.net (sri.MT.net [204.94.231.129]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA23015; Tue, 28 Mar 1995 10:16:20 -0800 Received: (from nate@localhost) by rocky.sri.MT.net (8.6.11/8.6.11) id LAA11924; Tue, 28 Mar 1995 11:17:56 -0700 Message-Id: <199503281817.LAA11924@rocky.sri.MT.net> From: Nate Williams Date: Tue, 28 Mar 1995 11:17:56 -0700 In-Reply-To: "Nate Williams" "cvs commit: src/share/mk bsd.lib.mk" (Mar 28, 9:54) Reply-To: Nate Williams X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: CVS-commiters@freefall.cdrom.com, cvs-share@freefall.cdrom.com Subject: Re: cvs commit: src/share/mk bsd.lib.mk Cc: current@FreeBSD.org, jkh@FreeBSD.org Sender: current-owner@FreeBSD.org Precedence: bulk > nate 95/03/28 09:54:12 > > Modified: share/mk bsd.lib.mk > Log: > *Really* strip out unused local symbols from shared objects. Okay, this should fix the problem Jordan was having with the static hash function being visible outside of the routine. Note, there are apparently still some 'stripping' bugs that exist in ld that Bruce pointed out, and I have a pretty good idea Bruce would like to see those symbols be visible, but until we get ld to be happy with the local symbols intact, the above change needed to be made. Current users. This change should cause you no problems whatsoever, but I would recommend re-building your libraries simply because there are symbols in them that don't need to be there, and those may cause linker problems at a later date with other programs who use some of the libraries internal symbols. This will cause the libraries for 2.1R to be safe with the current ld. Nate