Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Jan 2001 21:31:27 +0100
From:      Dirk Froemberg <dirk@FreeBSD.org>
To:        Peter Pentchev <roam@orbitel.bg>
Cc:        Radovan Gibala <gigi@agraf.sk>, ports@FreeBSD.org
Subject:   Re: MySQL and BerkleyDB
Message-ID:  <20010123213126.A46311@physik.TU-Berlin.DE>
In-Reply-To: <20010123144920.I2376@ringworld.oblivion.bg>; from roam@orbitel.bg on Tue, Jan 23, 2001 at 02:49:20PM %2B0200
References:  <3A6C158C.7F8794B1@agraf.sk> <20010122185314.D5657@ringworld.oblivion.bg> <20010123144920.I2376@ringworld.oblivion.bg>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 23, 2001 at 02:49:20PM +0200, Peter Pentchev wrote:
> On Mon, Jan 22, 2001 at 06:53:15PM +0200, Peter Pentchev wrote:
> > On Mon, Jan 22, 2001 at 12:12:12PM +0100, Radovan Gibala wrote:
> > > Is there any possibility to get a port for MySQL with BerkleyDB support
> > > ?
> > > I realy need the transaction support and I'd like to build MySQL from a
> > > port.
> > 
> > I'm currently working on a patch to the MySQL port to allow specifying
> > charsets (the --with-charset and --with-extra-charsets configure script
> > options).  I'll throw in Berkeley DB there for good measure.  Expect
> > patches tomorrow, and hopefully, if they do not screw up things very
> > badly, Dirk may include them sometime soon :)
> 
> OK, here's the patch as promised.  WITH_CHARSET=charset defines the
> primary charset (Latin-1 is the MySQL default), WITH_XCHARSET=list
> defines the other compiled-in charsets (may be 'all'), and WITH_BDB=yes
> (or simply -DWITH_BDB) compiles in Berkeley DB support.
> 
> You'd need the patch Dirk posted for the databases/db3 port.
> 
> Hmm.  A question to Dirk:  The configure script needed to be patched
> to look for libdb3.so instead of libdb.so (-ldb3).  I could have
> patched aclocal.m4, then specified USE_AUTOCONF and called aclocal;
> I chose to run a Perl regex on the configure script itself.  This is
> cheaper, and less error-prone for this particular MySQL version; it is,
> however, more error-prone for future MySQL versions, where this blind
> replacement could garble something else.  How do you feel about it?

I decided to include BDB as part of the mysql build. So the patching
-ldb -> -ldb3 isn't neccessary any longer. (But I would have included
it in patch-ag... 8-)

Is there any reason why you made the BDB part optional? I'd like to
include it generally.

	Regards Dirk

-- 
Dirk Froemberg

FreeBSD: The Power to Serve!		http://www.FreeBSD.org/


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010123213126.A46311>