1) Add AX_CHECK_MYSQL in configure.ac 2) eautoreconf 3) configure Result : Testing if MySQL was installed to common source/binary directory checking for mysql... no Testing if MySQL was installed to common package manager directory checking for mysql... yes checking /usr/include/mysql/mysql_version.h/mysql_version.h usability... no checking /usr/include/mysql/mysql_version.h/mysql_version.h presence... no checking for /usr/include/mysql/mysql_version.h/mysql_version.h... no checking /usr/include/mysql_version.h/mysql_version.h usability... no checking /usr/include/mysql_version.h/mysql_version.h presence... no checking for /usr/include/mysql_version.h/mysql_version.h... no checking if /usr/lib/mysql/plugin/ exists...... yes checking for mysql... /usr/bin/ checking yes/include/mysql/mysql_version.h/mysql_version.h usability... no checking yes/include/mysql/mysql_version.h/mysql_version.h presence... no checking for yes/include/mysql/mysql_version.h/mysql_version.h... no checking yes/include/mysql_version.h/mysql_version.h usability... no checking yes/include/mysql_version.h/mysql_version.h presence... no checking for yes/include/mysql_version.h/mysql_version.h... no checking if yes/lib/mysql/plugin/ exists...... no checking if yes/lib/plugin/ exists...... no checking for mysql... (cached) /usr/bin/ configure: WARNING: Could not find directory containing MySQL includes. The MySQL development library may not be installed. If development library is installed\, please designate the command\,plugin\,and include directories manually with --with-mysql-command\, --with-mysql-plugin\, and --with-mysql-include checking MySQL Architecture... 64 checking MySQL Version... 5.5.30 checking if MySQL install supports Plugins... yes checking /usr//include/mysql/mysql_version.h/mysql_version.h usability... no checking /usr//include/mysql/mysql_version.h/mysql_version.h presence... no checking for /usr//include/mysql/mysql_version.h/mysql_version.h... no checking /usr//include/mysql_version.h/mysql_version.h usability... no checking /usr//include/mysql_version.h/mysql_version.h presence... no checking for /usr//include/mysql_version.h/mysql_version.h... no checking if /usr//lib/mysql/plugin/ exists...... yes checking for mysql... (cached) /usr/bin/
Sorry, first log is incorrect: Testing if MySQL was installed to common source/binary directory checking for mysql... no Testing if MySQL was installed to common package manager directory checking for mysql... yes checking /usr/include/mysql/mysql_version.h/mysql_version.h usability... no checking /usr/include/mysql/mysql_version.h/mysql_version.h presence... no checking for /usr/include/mysql/mysql_version.h/mysql_version.h... no checking /usr/include/mysql_version.h/mysql_version.h usability... no checking /usr/include/mysql_version.h/mysql_version.h presence... no checking for /usr/include/mysql_version.h/mysql_version.h... no checking if /usr/lib/mysql/plugin/ exists...... yes checking for mysql... /usr/bin/ checking yes/include/mysql/mysql_version.h/mysql_version.h usability... no checking yes/include/mysql/mysql_version.h/mysql_version.h presence... no checking for yes/include/mysql/mysql_version.h/mysql_version.h... no checking yes/include/mysql_version.h/mysql_version.h usability... no checking yes/include/mysql_version.h/mysql_version.h presence... no checking for yes/include/mysql_version.h/mysql_version.h... no checking if yes/lib/mysql/plugin/ exists...... no checking if yes/lib/plugin/ exists...... no checking for mysql... (cached) /usr/bin/ configure: WARNING: Could not find directory containing MySQL includes. The MySQL development library may not be installed. If development library is installed\, please designate the command\,plugin\,and include directories manually with --with-mysql-command\, --with-mysql-plugin\, and --with-mysql-include checking MySQL Architecture... 64 checking MySQL Version... 5.5.30 checking if MySQL install supports Plugins... yes
You should use this as a development package: copy and adapt the file you need to your project. You can contribute the changes back upstream. *** This bug has been marked as a duplicate of bug 388519 ***
(In reply to comment #2) > You should use this as a development package: copy and adapt the file you > need to your project. You can contribute the changes back upstream. I do not support the advice to “copy and adapt the file you need to your project”. True, if the .m4 macro does not work as it is, you should check if a new release of autoconf-archive (Gentoo’s package is behind, my fault) has a fixed version of the macro my checking autoconf-archive’s website. For this package, maybe working with upstream to fix the macro may work better than asking for Gentoo to fix it on your behalf since you are the one using the macro in your autoconf script. This package is provided in Gentoo because sometimes old packages using old versions of autoconf-archive macros break. Another reason this package exists which you as an autoconf script writer should be aware of is that some packages using autoconf-archive macros fail to use AC_CONFIG_MACRO_DIR in configure.ac and set ACLOCAL_AMFLAGS in Makefile.am. Please set those ;-). Sorry for the irrelevant blabble… > *** This bug has been marked as a duplicate of bug 388519 ***
(In reply to comment #3) ax_* m4 files are not common. you cannot rely on them being available in the system. so packages make local copies and ship them. it is not provided in Gentoo for packages in the tree to use to rebuild autotools. they're provided as an easy way for devs to include. if you need something more, then you communicate with upstream. the maintainers are pretty responsive. patching the package in Gentoo is pretty much not going to happen like ever. Jeroen is correct.
