Bug #20794 Errors when compiling on Solaris 10
Submitted: 30 Jun 2006 15:54 Modified: 3 Sep 2006 17:22
Reporter: Farhan Mashraqi Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:Revision 1543 OS:Solaris (Solaris 10)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: Engineering

[30 Jun 2006 15:54] Farhan Mashraqi 
Description:
When compiling mysql-gui-tools on a Solaris 10 box, the autogen.sh script (and the configure command) fails with the following error messages:

checking for catalogs to be installed...  ja de pt_BR pl
./configure: line 5551: ./po/POTFILES.in: No such file or directory
./configure: line 5573: syntax error near unexpected token `GLIB,'
./configure: line 5573: `PKG_CHECK_MODULES(GLIB, glib-2.0')

How to repeat:
Download the source tree and build on Solaris 10.

svn co http://svn.mysql.com/svnpublic/mysql-administrator/1.1 mysql-administrator
svn co http://svn.mysql.com/svnpublic/mysql-gui-common/trunk mysql-gui-common
cd mysql-gui-common
sh ./autogen.sh

Suggested fix:
Syntax error on line 5573 needs to be fixed.
[4 Jul 2006 7:25] Sveta Smirnova 
Output on my Solaris box:
...
checking for catalogs to be installed...  ja de pt_BR pl
./configure: line 5573: ./po/POTFILES.in: No such file or directory
./configure: line 5595: syntax error near unexpected token `GLIB,'
./configure: line 5595: `PKG_CHECK_MODULES(GLIB, glib-2.0)'

$pkg-config --version
0.20

Output on Linux:
./configure: line 5632: ./po/POTFILES.in: No such file or directory
checking for GLIB... configure: error: Package requirements (glib-2.0 libxml-2.0 >= 2.6.2) were not met:
...
$pkg-config --version
0.20
[3 Aug 2006 17:22] Alfredo Kojima 
The error you got is not specific to Solaris 10, but it is to pkg-config 0.20
I've fixed that in the svn repository, please check if it works for you now.
[3 Sep 2006 23:00] Bugs System 
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".