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.
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. 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.
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. No idea what it's
trying to tell me, or how to proceed from there. Can't find any Google
search hits on the problems either. Suggestions?
-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
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-developers
