From owner-freebsd-current  Mon Sep 23 04:05:33 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA04020
          for current-outgoing; Mon, 23 Sep 1996 04:05:33 -0700 (PDT)
Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA03993
          for <current@FreeBSD.ORG>; Mon, 23 Sep 1996 04:05:28 -0700 (PDT)
Received: from baloon.mimi.com (sjx-ca12-08.ix.netcom.com [199.182.128.136]) by dfw-ix9.ix.netcom.com (8.6.13/8.6.12) with ESMTP id EAA26666; Mon, 23 Sep 1996 04:04:17 -0700
Received: (from asami@localhost) by baloon.mimi.com (8.7.5/8.6.12) id EAA03080; Mon, 23 Sep 1996 04:04:15 -0700 (PDT)
Date: Mon, 23 Sep 1996 04:04:15 -0700 (PDT)
Message-Id: <199609231104.EAA03080@baloon.mimi.com>
To: bde@zeta.org.au
CC: bde@zeta.org.au, current@FreeBSD.ORG, jhay@mikom.csir.co.za
In-reply-to: <199609230439.OAA04610@godzilla.zeta.org.au> (message from Bruce Evans on Mon, 23 Sep 1996 14:39:05 +1000)
Subject: Re: Some shared library problems
From: asami@FreeBSD.ORG (Satoshi Asami)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

 * >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.)
 * 
 * Perhaps there is no problem if you actually run -current.  In -current
 * there is a /usr/lib/compat directory containing libfakegnumalloc.so.2.0
 * -> libgnumalloc.so.2.0.  Applications linked to old libgnumalloc's
 * should find this and no other versions of libgnumalloc, and use the
 * better version of malloc() in libc.

I know that, what I mean is if we leave libgnumalloc.so.1.0 in
/usr/lib, and someone has a configure script that searches for
libgnumalloc, it will find it in /usr/lib and use it.  Also, a program
with a (bogus) Makefile that contains -lgnumalloc will compile.

IMO a shared library that is not intended for use by ld shouldn't be
in /usr/lib (unless it's an older version of another library that's
also in /usr/lib, in which case it's harmless).  That's the reason why
we have /usr/lib/compat and ldconfig.

Satoshi