Bug 52633 – MySQL ebuild 4.0.18-r2 failed

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Collin Starkweather 2004-05-31 15:19:53 UTC]

Trying to update MySQL, I get

item_cmpfunc.h: In constructor `
   Item_func_coalesce::Item_func_coalesce(List<Item>&)':
item_cmpfunc.h:250: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
if g++ -DMYSQL_SERVER -DDEFAULT_MYSQL_HOME="\"/usr\"" -DDATADIR="\"/var/lib/mysql\"" -DSHAREDIR="\"/usr/share/mysql\"" -DHAVE_CONFIG_H -I. -I. -I.. -I../bdb/build_unix -I./../include -I./../regex -I. -I../include -I.     -O3 -DDBUG_OFF -O2 -mcpu=i686 -pipe -felide-constructors -fno-exceptions -fno-rtti  -fno-implicit-templates -fno-exceptions -fno-rtti -MT item_strfunc.o -MD -MP -MF ".deps/item_strfunc.Tpo" \
  -c -o item_strfunc.o `test -f 'item_strfunc.cc' || echo './'`item_strfunc.cc; \
then mv -f ".deps/item_strfunc.Tpo" ".deps/item_strfunc.Po"; \
else rm -f ".deps/item_strfunc.Tpo"; exit 1; \
fi
The bug is not reproduceable, so it is likely a hardware or OS problem
make[4]: *** [item_cmpfunc.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[4]: Leaving directory `/var/tmp/portage/mysql-4.0.18-r2/work/mysql-4.0.18/sql'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/mysql-4.0.18-r2/work/mysql-4.0.18/sql'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/var/tmp/portage/mysql-4.0.18-r2/work/mysql-4.0.18/sql'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/mysql-4.0.18-r2/work/mysql-4.0.18'
make: *** [all] Error 2

!!! ERROR: dev-db/mysql-4.0.18-r2 failed.
!!! Function src_compile, Line 156, Exitcode 2
!!! compile problem

I don't quite get what is meant by "The bug is not reproduceable, so it is likely a hardware or OS problem".  I've never had a problem upgrading MySQL yet, and I've had it running on this box about 18 months now.


Reproducible: Always
Steps to Reproduce:
1. emerge -u mysql
2. 
3.

Actual Results:  
I received the above message and emerge exited.

Expected Results:  
MySQL 4.0.18-r2 should have been updated.

www root # emerge info
Portage 2.0.50-r7 (default-x86-1.4, gcc-3.3.2, glibc-2.3.2-r9, 2.4.22-gentoo-r5)
=================================================================
System uname: 2.4.22-gentoo-r5 i686 Pentium III (Coppermine)
Gentoo Base System version 1.4.3.13
Autoconf: sys-devel/autoconf-2.58-r1
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O2 -mcpu=i686 -pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /etc/tomcat /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/share/config /var/qmail/alias /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O2 -mcpu=i686 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache sandbox"
GENTOO_MIRRORS="http://gentoo.oregonstate.edu
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage"
USE="X apm arts avi berkdb crypt cups encode esd foomaticdb gdbm gif gnome gpm
gtk gtk2 imlib java jpeg kde libg++ libwww mad mikmod motif mpeg mysql ncurses
nls oggvorbis opengl oss pam pdflib perl png python qt quicktime readline sdl
slang spell ssl svga tcpd truetype x86 xml2 xmms xv zlib"

www root #

[Comment 1 Collin Starkweather 2004-05-31 20:22:03 UTC]

Curious.  I performed another emerge and it merged just fine:

*  dev-db/mysql
      Latest version available: 4.0.18-r2
      Latest version installed: 4.0.18-r2
      Size of downloaded files: 13,108 kB
      Homepage:    http://www.mysql.com/
      Description: A fast, multi-threaded, multi-user SQL database server
      License:     GPL-2

It always makes me nervous when things fix themselves.

[Comment 2 Robin Johnson 2004-05-31 23:09:48 UTC]

the mysql compile is one of the most challenging in terms of how it taxes a system.

it can be avoided by having more memory/swap (i've seen a gcc process use 1Gb+ of memory during a mysql compile), or avoiding specific CFLAGS that require larger allocations of memory.