I have set the berkdb use flag for dev-db/mysql in /etc/portage/package.use, but MySQL 5.0.19 seems to be compiled without BerkeleyDB support, as you can see in the output below. # emerge -pv dev-db/mysql These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild R ] dev-db/mysql-5.0.19 +berkdb +big-tables +cluster -debug -embedded +extraengine +max-idx-128 -minimal -perl (-selinux) -srvdir +ssl -static 4 kB Total size of downloads: 4 kB # echo 'SHOW STORAGE ENGINES;' | mysql -u root -p -t Enter password: +------------+----------+----------------------------------------------------------------+ | Engine | Support | Comment | +------------+----------+----------------------------------------------------------------+ | MyISAM | DEFAULT | Default engine as of MySQL 3.23 with great performance | | MEMORY | YES | Hash based, stored in memory, useful for temporary tables | | InnoDB | YES | Supports transactions, row-level locking, and foreign keys | | BerkeleyDB | NO | Supports transactions and page-level locking | | BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | | EXAMPLE | NO | Example storage engine | | ARCHIVE | YES | Archive storage engine | | CSV | YES | CSV storage engine | | ndbcluster | DISABLED | Clustered, fault-tolerant, memory-based tables | | FEDERATED | YES | Federated MySQL storage engine | | MRG_MYISAM | YES | Collection of identical MyISAM tables | | ISAM | NO | Obsolete storage engine | +------------+----------+----------------------------------------------------------------+ # emerge info Portage 2.0.54 (default-linux/amd64/2006.0, gcc-3.4.4, glibc-2.3.5-r2, 2.6.15-gentoo-r7 x86_64) ================================================================= System uname: 2.6.15-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.14 dev-lang/python: 2.4.2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/ ftp://ftp.gentoo.mesh-solutions.com/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo" LANG="en_US.utf-8" LINGUAS="de en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 apache2 avi bitmap-fonts bzip2 cjk cli crypt ctype cups curl dba eds emboss encode expat fastbuild foomaticdb force-cgi-redirect ftp gd gif gstreamer gtk2 iconv imlib ipv6 java jpeg lzw lzw-tiff memlimit mp3 mpeg mysql ncurses nls nptl opengl pam pcre pdflib php png posix quicktime readline session simplexml soap sockets spell spl sqlite ssl tcpd threads tiff tokenizer truetype truetype-fonts type1-fonts udev unicode xml xml2 xsl xv zlib linguas_de linguas_en userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LC_ALL, LDFLAGS
has been removed months ago for many archs, it should be time to check again if it's working good on the disabled archs. Relevant part of the ebuild is the following: ---------- #The following fix is due to a bug with bdb on sparc's. See: #http://www.geocrawler.com/mail/msg.php3?msg_id=4754814&list=8 # it comes down to non-64-bit safety problems if useq "sparc" || useq "alpha" || useq "hppa" || useq "mips" \ || useq "amd64" || mysql_check_version_range "5.01.00.00 to 5.01.06.99" then ewarn "bdb berkeley-db disabled due to arch or version" myconf="${myconf} --without-berkeley-db" else #TODO berkdb in 5.1 need to be worked on useq "berkdb" && \ ! mysql_check_version_range "5.01.00.00 to 5.01.08.99" \ && myconf="${myconf} --with-berkeley-db=./bdb" \ || myconf="${myconf} --without-berkeley-db" fi ----------
BerkDB is disabled for a couple of archs (alpha, amd64, hppa, mips, sparc), since it's known to be unstable and problematic, a message notifies the user of this. Also BerkDB is going to be removed by upstream in future MySQL releases, so better to not use it anyway. Best regards, CHTEKK.
*** Bug 200480 has been marked as a duplicate of this bug. ***
