From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pete Zaitcev <zaitcev@redhat.com>
Subject: Re: [Patch 1/1] CLD: fix crash in __mutex_get_max (libdb-4.7.so) on
 F13
Date: Sun, 29 Nov 2009 19:05:38 -0700
Message-ID: <20091129190538.6e791faa@redhat.com>
References: <20091129181744.578f4b20@redhat.com>
	<4B132225.6020505@garzik.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Return-path: <hail-devel-owner@vger.kernel.org>
In-Reply-To: <4B132225.6020505@garzik.org>
Sender: hail-devel-owner@vger.kernel.org
List-ID: <hail-devel.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>

On Sun, 29 Nov 2009 20:38:45 -0500, Jeff Garzik <jeff@garzik.org> wrote:
> On 11/29/2009 08:17 PM, Pete Zaitcev wrote:

> > Fedora 13 comes with db4.8 and apparently the compat-db4.7 is bust.
> > Let us link with 4.8 as a workaround.

> 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.

Aww, I didn't realize how it worked. Could you add this to the commit
message, in case?

-- Pete