Intel® C++ Compiler
Community support and assistance for creating C++ code that runs on platforms based on Intel® processors.
The Intel sign-in experience has changed to support enhanced security controls. If you sign in, click here for more information.
7782 Discussions

php 5.3.3 compiling crashes after compiling mysql 5.1.50



After several tests I'm ready to report a bug, but not sure if the bug related to mysql or icc.. The problem is thatphp 5.3.3 compiling crashes after compiling mysql 5.1.50. There is no any crashes on php 5.3.3 after compiling previous mysql 5.1.49..


/usr/local/mysql//include/mysql/my_global.h(626): catastrophic error: could not open source file "my_compiler.h"
compilation aborted for /root/src/php-5.3.3/ext/mysqli/mysqli.c (code 4)
make: *** [ext/mysqli/mysqli.lo] Error 1

My system:

CentOS 5.5 64-bit

Intel C++ Compiler for Linux 11.1.073 intel64

2Gb RAM,Intel Pentium Processor E2160

Is that an ICC problem? Or should I go to the mysql support?

0 Kudos
3 Replies
New Contributor II

By all means, this seems not a bug in either (mysql or ICC).

Did you followANY one of these which fixes the problem:--

1) This is easily fixed. After running 'make install' during the source installation process,

simply fire off the following command:

cp /usr/local/src/mysql-5.1.50/include/my_compiler.h


PHP 5.3.3 will now build the mysqli module with MySQL 5.1.50 from source.

2) ./configure --with-mysql=mysqlnd --with-mysqli=mysqlnd --with-pdo-mysql=mysqlnd

For more details on the exact bug, take a look at :--

Please let me know if theese work on your CentOS as well..


Ok, thank you for the answer! I've tried to run the command (below) before running 'make' and compilation finished without any problem :

cp /root/src/mysql-5.1.50/include/my_compiler.h /usr/local/mysql/include/mysql/my_compiler.h

It is a really bug of mysql 5.1.50 and will be fixed in 5.1.51

New Contributor II
yes, that is the required workaround. Usually, mysql havinga large publicrecord of current and past bugs, and they also have the temp workarounds provided so you can proceed with that before the "fixed" version is released.
Glad to know it fixed the problem.