Bug 44658 – MYSQL 4.0.18 crash while compiling

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Danilo 2004-03-14 04:50:07 UTC]

Whenever i try to emerge mysql-4.0.18 it crashes with the message:

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 -march=pentium3 -fomit-frame-pointer -felide-constructors -fno-exceptions -fno-rtti  -fno-implicit-templates -fno-exceptions -fno-rtti -MT sql_show.o -MD -MP -MF ".deps/sql_show.Tpo" \
  -c -o sql_show.o `test -f 'sql_show.cc' || echo './'`sql_show.cc; \
then mv -f ".deps/sql_show.Tpo" ".deps/sql_show.Po"; \
else rm -f ".deps/sql_show.Tpo"; exit 1; \
fi
sql_list.h: In member function `T* List_iterator_fast<T>::operator++(int) [with 
   T = char]':
sql_list.h:166: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://bugs.gentoo.org/> for instructions.
The bug is not reproduceable, so it is likely a hardware or OS problem
make[4]: *** [sql_show.o] Error 1
make[4]: Leaving directory `/var/tmp/portage/mysql-4.0.18/work/mysql-4.0.18/sql'
make[3]: *** [install-am] Error 2
make[3]: Leaving directory `/var/tmp/portage/mysql-4.0.18/work/mysql-4.0.18/sql'
make[2]: *** [install-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/mysql-4.0.18/work/mysql-4.0.18/sql'
make[1]: *** [install] Error 2
make[1]: Leaving directory `/var/tmp/portage/mysql-4.0.18/work/mysql-4.0.18/sql'
make: *** [install-recursive] Error 1

!!! ERROR: dev-db/mysql-4.0.18 failed.
!!! Function src_install, Line 164, Exitcode 2
!!! (no error message)


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

Actual Results:  
The build process failed

[Comment 1 Robin Johnson 2004-03-14 05:12:33 UTC]

lower your cflags, or add more ram/swap to your machine.
compiling mysql can use nearly 1Gb of memory with some cflags due to it's complexity.

[Comment 2 Danilo 2004-03-14 05:26:27 UTC]

Created attachment 27348 [details]
Mem usage

[Comment 3 Danilo 2004-03-14 05:29:08 UTC]

It is not using tall the ram/swap, look at the attachmen. I have 128MB ram / 512 swap. It used only 86.8 MB of the swap.

[Comment 4 Danilo 2004-03-14 05:30:29 UTC]

It is not using all the ram/swap, look at the attachment. I have 128MB ram / 512 swap. It used only 86.8 MB of the swap.

[Comment 5 Robin Johnson 2004-03-14 05:47:13 UTC]

your graph has nowhere near enough time resolution to see the memory usage of a single gcc call.

run "vmstat 1" (from sys-apps/procps)
while doing the emerge, and see the large memory usage.

then reduce the cflags and see it work fine.