From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeff Garzik <jeff@garzik.org>
Subject: Re: [Patch 1/1] CLD: fix crash in __mutex_get_max (libdb-4.7.so)
 on F13
Date: Wed, 02 Dec 2009 05:40:25 -0500
Message-ID: <4B164419.3060507@garzik.org>
References: <20091129181744.578f4b20@redhat.com>	<4B132225.6020505@garzik.org> <20091201181812.15a28bd2@redhat.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <hail-devel-owner@vger.kernel.org>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:sender:message-id:date:from
         :user-agent:mime-version:to:cc:subject:references:in-reply-to
         :content-type:content-transfer-encoding;
        bh=wBiT0Tr2yoeEofVZYGbCQG7IPYf/XWV85Y5zvs88i0w=;
        b=rOcA+rKodebuhqmWqA14rEdB3/B+JqVprowROOvdDBFV8KmIcr5OtFGeK552/iDGig
         5QJlJpV1katL95nIf2rMIzNM4r4Zx2DkaEi9j7ncmuF1VjwVAuxSp4xrg4dimpGgeLa0
         eyJUQPYAZiYK6OciM+kR27/lySUuzN2C3aGb4=
In-Reply-To: <20091201181812.15a28bd2@redhat.com>
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Project Hail List <hail-devel@vger.kernel.org>

On 12/01/2009 08:18 PM, Pete Zaitcev wrote:
> On Sun, 29 Nov 2009 20:38:45 -0500
> Jeff Garzik<jeff@garzik.org>  wrote:
>
>> Interesting...  I recall the root cause clearly, now:  /usr/include/db.h
>> always refers to the latest installed db4, even if compat-db{,45,46} is
>> installed.  Our configure recipe links with the most recent db4 listed
>> in configure.ac, combined with the installed /usr/include/db.h.  Thus,
>> each new db4 version produces a mismatch.
>
> I solicited suggestions on a blog, and someone asked why we don't
> use db without specific version. I assumed we do it so we don't
> get linked with something ancient like db3. Is that so? If yes,
> how about something like this:

libdb does not exist anywhere but more recent versions of Linux.  That 
link does not exist on older, non-RHL Linux's, nor on FreeBSD, nor on 
Solaris.  The proposed configure change would actually make us much 
-less- portable, unfortunately.

The ideal is somewhat close to what a LJ poster proposed:
* include from $include_dir/$db_version
* link from libdb-$db_version
* provide pkgconfig info that gives us precise location information

That's how, eg. glib/gtk+ 1.x can co-exist with glib/gtk+ 2.x.

But we lack a time machine to make this happen :/

	Jeff