[Monetdb-developers] test missing on pkg-config in clients configure
Hi all, I got the following error message due to a missing pkg-config installation—Perhaps there could be a better error message: /home/rittinge/MonetDB.hg/clients/configure: line 2894: syntax error near unexpected token `monetdbtools,' /home/rittinge/MonetDB.hg/clients/configure: line 2894: `PKG_CHECK_MODULES(monetdbtools, monetdb-stream >= $req_monetdb_ver' -- Jan Rittinger Lehrstuhl Datenbanken und Informationssysteme Wilhelm-Schickard-Institut für Informatik Eberhard-Karls-Universität Tübingen http://www-db.informatik.uni-tuebingen.de/team/rittinger
On 09-10-2010 00:24:24 +0200, Jan Rittinger wrote:
Hi all,
I got the following error message due to a missing pkg-config installation—Perhaps there could be a better error message:
Did you get errors from bootstrap? configure should never hold the m4 macros.
/home/rittinge/MonetDB.hg/clients/configure: line 2894: syntax error near unexpected token `monetdbtools,' /home/rittinge/MonetDB.hg/clients/configure: line 2894: `PKG_CHECK_MODULES(monetdbtools, monetdb-stream >= $req_monetdb_ver'
On Oct 9, 2010, at 08:16, Fabian Groffen wrote:
On 09-10-2010 00:24:24 +0200, Jan Rittinger wrote:
Hi all,
I got the following error message due to a missing pkg-config installation—Perhaps there could be a better error message:
Did you get errors from bootstrap? configure should never hold the m4 macros.
No errors with respect to pkg-config: $ ./bootstrap ... configure.in:166: warning: macro `AM_ICONV' not found in library patching file aclocal.m4 Hunk #1 succeeded at 439 (offset -5947 lines). configure.in:166: error: possibly undefined macro: AM_ICONV If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. I'm also a little bit puzzled that you ask about m4 as the exact line 'PKG_CHECK_MODULES(monetdbtools, monetdb-stream...' is already in configure.ag.
/home/rittinge/MonetDB.hg/clients/configure: line 2894: syntax error near unexpected token `monetdbtools,' /home/rittinge/MonetDB.hg/clients/configure: line 2894: `PKG_CHECK_MODULES(monetdbtools, monetdb-stream >= $req_monetdb_ver'
------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- Jan Rittinger Lehrstuhl Datenbanken und Informationssysteme Wilhelm-Schickard-Institut für Informatik Eberhard-Karls-Universität Tübingen http://www-db.informatik.uni-tuebingen.de/team/rittinger
On 09-10-2010 14:33:09 +0200, Jan Rittinger wrote:
On Oct 9, 2010, at 08:16, Fabian Groffen wrote:
On 09-10-2010 00:24:24 +0200, Jan Rittinger wrote:
Hi all,
I got the following error message due to a missing pkg-config installation—Perhaps there could be a better error message:
Did you get errors from bootstrap? configure should never hold the m4 macros.
No errors with respect to pkg-config:
$ ./bootstrap ... configure.in:166: warning: macro `AM_ICONV' not found in library patching file aclocal.m4 Hunk #1 succeeded at 439 (offset -5947 lines). configure.in:166: error: possibly undefined macro: AM_ICONV If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
I'm also a little bit puzzled that you ask about m4 as the exact line 'PKG_CHECK_MODULES(monetdbtools, monetdb-stream...' is already in configure.ag.
Please just install pkg-config, and it's m4 macro that comes with it (-devel?) And also consider isntalling gettext(-devel?), to get the necessary AM_ICONV macro.
On Oct 9, 2010, at 23:20, Fabian Groffen wrote:
On 09-10-2010 14:33:09 +0200, Jan Rittinger wrote:
On Oct 9, 2010, at 08:16, Fabian Groffen wrote:
On 09-10-2010 00:24:24 +0200, Jan Rittinger wrote:
Hi all,
I got the following error message due to a missing pkg-config installation—Perhaps there could be a better error message:
Did you get errors from bootstrap? configure should never hold the m4 macros.
No errors with respect to pkg-config:
$ ./bootstrap ... configure.in:166: warning: macro `AM_ICONV' not found in library patching file aclocal.m4 Hunk #1 succeeded at 439 (offset -5947 lines). configure.in:166: error: possibly undefined macro: AM_ICONV If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation.
I'm also a little bit puzzled that you ask about m4 as the exact line 'PKG_CHECK_MODULES(monetdbtools, monetdb-stream...' is already in configure.ag.
Please just install pkg-config, and it's m4 macro that comes with it (-devel?) And also consider isntalling gettext(-devel?), to get the necessary AM_ICONV macro.
Fabian, that's where my mail started from. Installing pkg-config got the intial strange error message sorted out. I was just wondering that pkg-config itself is not checked by configure (to give a more useful error message). As to AM_ICONV—this seems to be not optional as a call to AM_ICONV still resides in the generated configure file... -- Jan Rittinger Lehrstuhl Datenbanken und Informationssysteme Wilhelm-Schickard-Institut für Informatik Eberhard-Karls-Universität Tübingen http://www-db.informatik.uni-tuebingen.de/team/rittinger
On 10-10-2010 09:41:49 +0200, Jan Rittinger wrote:
that's where my mail started from. Installing pkg-config got the intial strange error message sorted out. I was just wondering that pkg-config itself is not checked by configure (to give a more useful error message).
configure does! However, you need to be able to generate it properly. I thought autoconf should/would bail on missing macros, but in any case, that's beyond our ability to fix.
As to AM_ICONV—this seems to be not optional as a call to AM_ICONV still resides in the generated configure file...
Which is wrong, but probably causes your interpreter to simply emit some error about a missing/undefined function, since the macro call has no arguments. Proper bootstrapping is hard, maybe we could extend the bootstrap script to check these requirements and just refuse to work if missing.
participants (2)
-
Fabian Groffen -
Jan Rittinger