On 12/01/2009 08:18 PM, Pete Zaitcev wrote:
On Sun, 29 Nov 2009 20:38:45 -0500 Jeff Garzik<jeff@xxxxxxxxxx> 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 -- To unsubscribe from this list: send the line "unsubscribe hail-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
