MySQL Bugs: #48619: Incorrect error message when running configure for MySQL Proxy 0.7.2 (glib-2.0)

Bug #48619	Incorrect error message when running configure for MySQL Proxy 0.7.2 (glib-2.0)
Submitted:	9 Nov 2009 4:23	Modified:	25 Nov 2009 15:52
Reporter:	Roel Van de Paar	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Proxy: Install/Config	Severity:	S2 (Serious)
Version:	0.7.2	OS:	Linux (Ubuntu 9.0.4)
Assigned to:		CPU Architecture:	Any

Description:
$./configure --with-mysql=/proxy/mysql-5.1.40-proxied/bin/mysql_config
[...]
checking for GLIB... configure: error: Package requirements (glib-2.0 >= 2.16.0) were not met:

No package 'glib-2.0' found

----

libglibmm-2.4-1c2a (2.20.0-0ubuntu2) was installed on the system.

How to repeat:
Install proxy 0.7.2 on Ubuntu 9.0.4 without having libglibmm-2.4-dev installed.

Suggested fix:
1. Glib 2.2 was installed on the system, thus error seems incorrect.
2. Error does not notify of need for -dev package to be installed.

Workaround: Installing libglibmm-2.4-dev (2.20.0-0ubuntu2) and it's dependencies resolved the error.

Should have mentioned libglib2.0-0 (2.20.1-0ubuntu2.1) / libglib2.0-dev (2.20.1-0ubuntu2.1) instead.

Verifying as D4

Diego Medina writes: 
Hi Roel,

Thanks for your bug report.

I agree that having a detailed message telling you the exact name of the package you need would be very helpful. 
But we do include that information on the INSTALL file.

We are looking into adding a message that one error, it would direct people to the INSTALL file.

Thanks

Diego

Hi Diego,

OK so once there would be an error, people would be directed to the INSTALL file. 

That would be acceptable if there would be no (incorrect) mention of a 'glib-2.0' package.

As such, can we leave this bug open until either:

1. The current error message is removed, and people are directed to the INSTALL file instead.

   or (as per the above)

2. The current error message is changed to list the correct package.

Many others running into this:

http://www.google.com.au/search?q=%2B%22No+package+%27glib-2.0%27+found%22+%2Bproxy+%2Bmys...

Also, I could not locate this information in the INSTALL file?

roel@roel-ubuntu-vm:/proxy/mysql-proxy-0.7.2$ cat INSTALL | grep glib
roel@roel-ubuntu-vm:/proxy/mysql-proxy-0.7.2$ cat INSTALL | grep '-' | grep dev
roel@roel-ubuntu-vm:/proxy/mysql-proxy-0.7.2$

Diego Medina writes: 
Hi Roel,

How did you get the source of the mysql proxy?

I just went to the launchpad site

http://bazaar.launchpad.net/~mysql-proxy-developers/mysql-proxy/0.7/annotate/head%3A/INSTA...

and that file has an Ubuntu section:

{noformat}
  $ apt-get install \
      pkg-config \
      liblua5.1-0 \
      liblua5.1-dev \
      libevent-dev \
      libevent1  \
      libglib2.0-0 \
      libglib2.0-dev \
      libmysqlclient-dev

On Debian and Ubuntu you need to tell the configure script that it has to use 
"pkg-config lua5.1" to detect the lua-libriaries instead of the default 

"pkg-config lua".

  $ ./configure --with-lua=lua5.1
{noformat}

Is that information incorrect?

If that is the case, could you open a new bug against the INSTALL file, and add the correct names that we should include in the file?

Regarding showing the correct package name on the ./configure if an error occurs. This is actually hard to do, because different Linux flavors use different names for the "-dev" packages.

For example, in Fedora, the header files for glib2 are under the package name: glib2-devel

I have spoken with the developers, and they agree that sending users to the INSTALL file makes more sense than having to be so verbose on the ./configure file.
I may be asking a lot but, could you open another bug asking for such modification? And then we could close the other bugs that are in a way similar to this one.

Thanks a lot for bringing this to our attention.

Oh, and this is something that happens with other projects as well, just to name a few, if you try to build apache httpd or php from source, you will run into the same "name mismatch"

  -Diego

Mark Leith writes: 
This is not a bug with proxy - it's making sure that you have the right build environment (welcome to autotools :))