From owner-freebsd-current  Sun Sep 22 15:41:46 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id PAA24847
          for current-outgoing; Sun, 22 Sep 1996 15:41:46 -0700 (PDT)
Received: from dfw-ix11.ix.netcom.com (dfw-ix11.ix.netcom.com [206.214.98.11])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id PAA24809
          for <current@FreeBSD.org>; Sun, 22 Sep 1996 15:41:43 -0700 (PDT)
Received: from baloon.mimi.com (sjx-ca16-27.ix.netcom.com [199.35.223.155]) by dfw-ix11.ix.netcom.com (8.6.13/8.6.12) with ESMTP id PAA13982; Sun, 22 Sep 1996 15:40:48 -0700
Received: (from asami@localhost) by baloon.mimi.com (8.7.5/8.6.12) id PAA01324; Sun, 22 Sep 1996 15:40:16 -0700 (PDT)
Date: Sun, 22 Sep 1996 15:40:16 -0700 (PDT)
Message-Id: <199609222240.PAA01324@baloon.mimi.com>
To: bde@zeta.org.au
CC: current@FreeBSD.org, jhay@mikom.csir.co.za
In-reply-to: <199609211317.XAA18586@godzilla.zeta.org.au> (message from Bruce Evans on Sat, 21 Sep 1996 23:17:31 +1000)
Subject: Re: Some shared library problems
From: asami@FreeBSD.org (Satoshi Asami)
Sender: owner-current@FreeBSD.org
X-Loop: FreeBSD.org
Precedence: bulk

 * The installation of libfakegnumalloc is currently broken (it deletes all
 * versions of libgnumalloc.so from ${SHLIBDIR}).  I think it is supposed
 * to work by leaving old versions alone and putting a guaranteed-newer
 * version in the compat directory for future ld commands to find.

I don't think that was the intention.  The removal of all gnumalloc
shared libraries from /usr/lib was to prevent ported software
automatically detecting and using a shared libgnumalloc.  (The ld
commands are not supposed to find it, as it is empty anyway.)

 * 								    It
 * would be cleaner but too hard to mv old versions of libgnumalloc.so
 * to the compar directory.

It may be hard, but this is what we should do if we want to keep older 
versions.

Satoshi