Hi, On Wed, Aug 22, 2012 at 07:47:07PM +0300, Jukka Santala wrote:
SuSE Linux Enterprise Server 11 SP2, release in March. As already covered on the bug-tracker etc. old bison won't work, so I had to install latest version, 2.6.2 to build.
Are you using HG sources or a released source tarball? The latter is recommended and should not require bison at all ...
After that: make[5]: Entering directory `/opt/MonetDB/MonetDB-11.11.5/sql/server' /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I../include -I./../include -I../common -I./../common -I../storage -I./../storage -I../../clients/mapilib -I./../../clients/mapilib -I../../common/options -I./../../common/options -I../../common/stream -I./../../common/stream -I../../gdk -I./../../gdk -DLIBSQLSERVER -g -O2 -c -o libsqlserver_la-sql_scan.lo `test -f 'sql_scan.c' || echo './'`sql_scan.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I. -I../include -I./../include -I../common -I./../common -I../storage -I./../storage -I../../clients/mapilib -I./../../clients/mapilib -I../../common/options -I./../../common/options -I../../common/stream -I./../../common/stream -I../../gdk -I./../../gdk -DLIBSQLSERVER -g -O2 -c sql_scan.c -fPIC -DPIC -o .libs/libsqlserver_la-sql_scan.o In file included from sql_semantic.h:27, from sql_scan.c:29: sql_parser.h:191: error: conflicting types for 'sqlparse' y.tab.h:678: error: previous declaration of 'sqlparse' was here
No idea how to properly fix that, but added "#define YYPARSE_PARAM parm" at the front of sql_scan.c, which forces the prototype to retain the parameter.
Next problem, HowToStart.rst states: "Then in any directory (preferably a *new, empty* directory and *not* in the ``MonetDB`` top-level directory) give the command:: .../configure [<options>]", which is indeed recommended practice. Unfortunately, nobody has apparently ever done this.
I can ensure you, we do this, and only this several times per day, so you can assume that building MonetBD this way is very well tested ;-)
If configure and make are ran in a different directory from the source root, "make check" will fail to find monetdb5/modules/mal/mal_init.mal and who knows what else, giving long time of head-scratching.
Ok, I/we do admit that `make check` has not been used by us for a long time (at least not by myself), and thus, it might not work properly anymore. Hence, thank you very much for notifing us about it. We will either fix it, or remove it completely. We test MonetDB by running `Mtest.py`, (for now still?) separately in .../MonetDB/clients/ , .../MonetDB/monetdb5/ , .../MonetDB/sql/ , and .../MonetDB/geom/
After re-doing configure and make in the prohibited directory, make check will report: . opt_sql_append : Crashed!
* (opt_sql_append.test.out.FILTERED) significantly
* (opt_sql_append.test.err.FILTERED) significantly ....................................................................................................................................................................................................................................... * (recycle04.test.out.FILTERED) significantly ........................................................................................................................................................................................................................................................................... !ERROR: Testing FAILED SIGNIFICANTLY (2 out of 499 tests failed)
1 out of 499 tests resulted in a crash extras/mal_optimizer_template/opt_sql_append 1 out of 499 tests produced SIGNIFICANTLY different output mal/recycle04
To be frank, that sounds "significantly" like something translated by Google translator to/from some lesser known language.
Well, we don't need to understand this comment, do we?
No idea what it's trying to tell me,
MonetDB testing is mainly for internal/development use. The existence of a "quasi standard", without further documentation than (from HowToStart.rst) " This will perform a large number of tests, some are unfortunately still expected to fail, but most should go successfully. " might suggest differently. We'll consider making our documentation even more explicit on this. Thus, the above just tells you this: some of the tests did fail in your case. Most of the also fail with our nightly testing, cf., http://monetdb.cwi.nl/testweb/web/status.php?branch=Jul2012 and thus are not considered crucial.
or how to proceed from there.
Simply enjoy using MonetDB ;-)
Can't find any Google search hits on the problems either. Suggestions?
See above ;-) Thanks again, for trying all this and notifying us. Given that we never had any feedback on it before, we were not aware of the fact that people outside the core MonetDb developers team were using MonetDB's testing facilities, thus, we never spent more time on improving their documentation or making them more end-user friendly. We'll take your comments as tirgger to reconsiders this in some future release. Best, Stefan
-Jukka Santala
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- | Stefan.Manegold @ CWI.nl | DB Architectures (INS1) | | http://CWI.nl/~manegold/ | Science Park 123 (L321) | | Tel.: +31 (0)20 592-4212 | 1098 XG Amsterdam (NL) |