MySQL Bugs: #18448: MySQL make freezes computer

Bug #18448	MySQL make freezes computer
Submitted:	23 Mar 2006 7:59	Modified:	23 Mar 2006 15:29
Reporter:	Terry James	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.0.18	OS:	Linux (Linux Slackware 10.2)
Assigned to:		CPU Architecture:	Any

Description:
Using ./configure 

--prefix=/hdc5/MySQL5

after configure finishes with no errors,

make

results in a complete system freeze under a command console in KDE shell.

How to repeat:
Set a disk to be mounted as /dev/hdc5 and create the directories:

/Source

and

/MySQL5

create the directory /Source/MySQL5.0.18

untar the source to /Source/MySQL5.0.18 which will create the following tree:

/Source/MySQL5.0.18/MySQL-5.0.18

cd to /hdc5/Source/MySQL5.0.18/MySQL-5.0.18 and execute

./configure --prefix=/MySQL5

Execute:

make

Suggested fix:
I don't know yet and I have to submit this bug before the site logs me out.

*Note:

This worked almost flawlessly from a standard prompt without the gui running, neither X nor KDE.

I did notice using top that cc1 and cc1plus, cross compiles closing files, were hitting 99.7% cpu times and consider that perhaps GCC needs to regulate this better because anything over 80% cpu is out of bounds for any program.  Definitely a tasking priority problem here.  This probably collided head on with both X and KDE over timing and various file locks.

In threading the results will most often be a lock up with only 0.3% cpu available to manage the entire system outside of the compiler and gui's.

So the bug is related to head on collision with the graphical user interface system, it may be GCC's fault, it may be Linux' fault, and it could just as well be simply an exascerbation by the heavy load of compiling MySQL.

However, it must be noted that thus far only MySQL has exhibited this behavior.

Sounds like a memory/swapping problem to me. I know several users that compile mysql within a KDE or Gnome environment but have never heard of a problem like this ...

Regarding your question on prepared configure scripts: there is a collection of build scripts in the BUILD/ directory that comes with the source, e.g. BUILD/compile-pentium-debug-max, but the general idea of configure and the autotools is indeed that you can usually just run "configure; make; make install" without having to take care of distribution specific issues (unless needed libraries and header files have been installed in very strange places manually). A plain "configure" will not enable all product features though.