MySQL Bugs: #45616: Fixing build when building in other directory

Bug #45616	Fixing build when building in other directory
Submitted:	19 Jun 2009 13:48	Modified:	7 Jan 2014 15:49
Reporter:	Michal Hrusecky	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Compiling	Severity:	S3 (Non-critical)
Version:	5.1.35	OS:	Linux
Assigned to:	Daniel Fischer	CPU Architecture:	Any
Tags:	Contribution

Description:
I'm using a little bit unusual setup for building MySQL. I'm running configure and make from different directory then sources are and in recent versions of MySQL this stopped to work because make can't find some files. I noticed it first with version 5.1.33 but still apply in 5.1.35

How to repeat:
bzip2 -cd mysql-5.1.35.tar.bz2 | tar -xvf -
mkdir build
cd ./build
../mysql-5.1.35/configure
make

Suggested fix:
Will follow

This fixxes reported issue

Attachment: mysql-5.1.33-scripts-paths.patch (text/x-patch), 734 bytes.

Thank you for the report.

Verified as described.

Error:

Building mysql_fix_privilege_tables.sql
cat: mysql_system_tables.sql: No such file or directory
cat: mysql_system_tables_fix.sql: No such file or directory
make[1]: *** [mysql_fix_privilege_tables.sql] Error 1
make[1]: Leaving directory `/users/ssmirnova/src/mysql-5.1-build/scripts'
make: *** [all-recursive] Error 1

Hello Michal 

 In order for us to continue the process of reviewing your contribution
 to MySQL - We need you to review and sign the Sun|MySQL contributor
 agreement (the "SCA")

 The process is explained here:
 http://forge.mysql.com/wiki/Sun_Contributor_Agreement

 Getting a signed/approved SCA on file will help us facilitate your
 contribution-- this one, and others in the future.

 Thank you !

 Liz Drachnik  - Program Manager - MySQL

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Posted by developer:
 
This bug is auto tools specific and for 5.1. Since 5.1 is EOL'ed, it will not be fixed.