Hello,
Apologies if this is the improper place to be asking this. I'm a new user to
MonetDB, and I'm having trouble installing MonetDB/XQuery on Ubuntu 10.04
32-bit. Actually, the installation did seem to succeed (running the auto
install script from the super source tarball) and I can start MServer, but
with the error:
# MonetDB Server v4.40.2
# based on GDK v1.40.2
# not released
# Copyright (c) 1993-July 2008, CWI. All rights reserved.
# Copyright (c) August 2008-2010, MonetDB B.V.. All rights reserved.
# Compiled for i686-pc-linux-gnu/32bit with 32bit OIDs; dynamically linked.
# Detected 3.919 GiB (4208013312 bytes) main-memory.
# Visit http://monetdb.cwi.nl/ for further information.
!ERROR: moduleClient: module(pathfinder) load error.
The problem, its seems anyway, is during the configuration of pathfinder:
...
...
checking for signal.h... yes
checking return type of signal handlers... (cached) void
checking for strings.h... (cached) yes
checking for strcasecmp... yes
checking for xml2-config.32... no
checking for xml2-32-config... no
checking for xml2-config... no
checking for libxml/parser.h... no
configure: error: in `/home/rob/MonetDB':
configure: error: The libxml2 XML parsing library and/or include files were
not found or you have requested to not use it.
This is required dependence, core components like
the XML Schema import functionality depends on it.
See `config.log' for more details.
I do have libxml2 installed (by default with Lucid). I've run the pathfinder
configure script a few times, with the option --with-libxml2=*some
variations*, but I'm not really confident about what I'm doing. I was
wondering if anyone could point me in the right direction. Thanks.
-Rob
Dear users,
I'm currently struggling with concurrent access to MonetDB/SQL via JDBC.
Version: MonetDB server v5.20.4 (64-bit), based on kernel v1.38.4 (64-bit oids).
I might still have some concurrency issues with my own code, but
somehow I frequently end up with the following error message:
(while stress-testing by querying with 10 threads at the same time)
class java.sql.SQLException:
TypeException:user.s3_1[448]:'user.contains' undefined in: _1933:any
:= user.contains(_1929:str, _1931:str, _474:bit)
TypeException:user.s3_1[449]:'bat.insert' undefined in: _1934:any :=
bat.insert(_1923:bat[:oid,:bit], _1928:oid, _1933:any)
TypeException:user.s3_1[645]:'user.contains' undefined in: _1946:any
:= user.contains(_1942:str, _1944:str, _474:bit)
TypeException:user.s3_1[646]:'bat.insert' undefined in: _1947:any :=
bat.insert(_1938:bat[:oid,:bit], _1941:oid, _1946:any)
TypeException:user.s3_1[1042]:'user.contains' undefined in: _1959:any
:= user.contains(_1955:str, _1957:str, _474:bit)
TypeException:user.s3_1[1043]:'bat.insert' undefined in: _1960:any :=
bat.insert(_1951:bat[:oid,:bit], _1954:oid, _1959:any)
TypeException:user.s3_1[1226]:'user.contains' undefined in: _1974:any
:= user.contains(_1970:str, _1972:str, _474:bit)
TypeException:user.s3_1[1227]:'bat.insert' undefined in: _1975:any :=
bat.insert(_1964:bat[:oid,:bit], _1969:oid, _1974:any)
SQLException:SQLengine:Program contains errors
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.executeQuery(MonetConnection.java:2209)
nl.cwi.monetdb.jdbc.MonetConnection$ResponseList.processQuery(MonetConnection.java:1968)
nl.cwi.monetdb.jdbc.MonetStatement.internalExecute(MonetStatement.java:506)
nl.cwi.monetdb.jdbc.MonetStatement.execute(MonetStatement.java:347)
nl.cwi.monetdb.jdbc.MonetStatement.executeUpdate(MonetStatement.java:542)
Does anyone else have experienced such error messages before, or does
anyone have a clue to where to look?
(like too many open connections, concurrent access of the same
connection, querying a closed connection, or perhaps a bug inside
monetdb)?
Thanks,
Wouter
Hi,
I'd like to use Lefteris' RDF package on Debian. What do I have to do
to create and connect to a database as user on Debian?
I've installed the following packages:
# dpkg -l | grep -e monetdb
ii libmonetdb-client1 1.40.1-20101110
MonetDB database client libraries
ii libmonetdb1 1.40.1-20101110
database system for high-performance applications, libraries
ii libmonetdb5-server5 5.22.1-20101110
MonetDB database server version 5, libraries
ii libmonetdb5-sql2 2.40.1-20101110
MonetDB SQL libraries for monetdb5-server
ii monetdb-client 1.40.1-20101110
MonetDB database client
ii monetdb5-server 5.22.1-20101110
MonetDB database server version 5
ii monetdb5-sql 2.40.1-20101110
MonetDB SQL support for monetdb5
I can start MonetDB:
# /etc/init.d/monetdb5-sql start
Starting MonetDB SQL server: merovingian.
When I try do create the tables (as a user):
$ mclient -lsql create_tables.sql
user(aharth):
password:
merovingian: please specify a database
$
$ mclient -lsql create_tables.sql -d demo
user(aharth):
password:
merovingian: internal error while starting mserver, please refer to the logs
$
The log says:
2010-11-25 16:20:19 MSG merovingian[3685]: starting database 'demo', up
min/avg/max: 3s/4s/5s, crash average: 0.00 0.00 0.00 (2-2=0)
2010-11-25 16:20:19 ERR merovingian[3685]: client error: cannot start database
'demo': no .vaultkey found (did you create the database with `monetdb create demo`?)
I'm stuck here. How can I create a database as a user?
$ monetdb create demo2
permission denied
$
As root, I only can create a database in maintainance mode:
# monetdb create demo2
created database in maintenance mode: demo2
#
Any pointers to howto's that'll help?
Cheers,
Andreas.
I see --- if you consider it a bug, please file a detailed bug report including information & instructions to reporduce the problem as well as infornmation about the exact MonetDB version and OS you're using via http://bugs.MonetDB.org/
Stefan
----- Oorspronkelijk bericht -----
Van: Freddy Priyatna <freddy.priyatna(a)gmail.com>
Verzonden: maandag 25 oktober 2010 16:32
Aan: Communication channel for MonetDB users <monetdb-users(a)lists.sourceforge.net>
Onderwerp: Re: [MonetDB-users] Querying date type column in MonetDB
Hi Stefan,
Nope, the name of the column is "deliveryDays" :)
Freddy
2010/10/25 Stefan Manegold <Stefan.Manegold(a)cwi.nl>
> Hi Freddy,
>
> I don't think that the error you experience is triggered by the column
> type, but rather by the fact that your date column ha? a name - say "date" -
> that is a reserved key word in SQL an hence needs to be double-quoted
> according to the SQL standard (this is not a MonetDB specific choice, but a
> "feature" of the SQL standard) --- not knowing your table & column names, I
> can only guess, though ...
>
> Stefan
>
>
> ----- Oorspronkelijk bericht -----
> Van: Freddy Priyatna <freddy.priyatna(a)gmail.com>
> Verzonden: maandag 25 oktober 2010 16:03
> Aan: MonetDB-users <monetdb-users(a)lists.sourceforge.net>
> Onderwerp: [MonetDB-users] Querying date type column in MonetDB
>
> Dear All,
>
> I am new to MonetDB, so most likely my question will look obvious.
>
> I would like to ask, how can columns with date type is queried in monetdb.
> Based on my experience, it seems that date type columns need special
> treatment. It seems that the only way to query them is with the syntax
> "column_name" while other columns seems to work with the format
> table_name.column_name without the need of double quote. When I tried to
> query date column with the syntax table_name.column_name, it gave me an
> error "no such column"
>
> So my question is, is it true that the only way to query date columns is
> using "column_name" format? Another question will be, what happen if I need
> to query same name columns coming from different table?
>
> Thanks in advance,
> Freddy
>
>
> ------------------------------------------------------------------------------
> Nokia and AT&T present the 2010 Calling All Innovators-North America
> contest
> Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
> $10 million total in prizes - $4M cash, 500 devices, nearly $6M in
> marketing
> Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
> http://p.sf.net/sfu/nokia-dev2dev
> _______________________________________________
> MonetDB-users mailing list
> MonetDB-users(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/monetdb-users
>
I have a tab-delimited data file that is mostly ascii, but has a few hex
characters in it.
For example:
...
3263640152 ABC<99>
...
where <99> is a hex value for (tm) - trademark.
When I try and load this data file into monetdb, I get the following error:
[root@bidbtest ~]# /usr/local/MonetDB/bin/mclient -lsql --database=myschema
-t -s "COPY 20603 records into test_table from '/tmp/testdata.txt' using
delimiters '\t','\n','\"' null as '';"
user(root):monetdb
password:
MAPI = (monetdb) /usr/local/MonetDB/var/MonetDB5/dbfarm/mapi_socket
QUERY = COPY 20603 records into test_table from '/tmp/testdata.txt' using
delimiters '\t','\n','"' null as '';
ERROR = !SQLException:importTable:value 'failed to import table
Timer 790.415 msec
The table def is:
CREATE TABLE creative_dim (
id bigint NOT NULL,
headline varchar(100) DEFAULT NULL
)
How can I go about loading this file?
Ideally, I would like to get these characters loaded as is.
I saw that mclient has a -E flag that accepts an encoding type. However,
I'm not sure what to set it to for a file with ascii / hex data.
A complicating factor is that I don't know all the hex characters that are
in my file. I luckily spotted the <99>/tm one above as it was one of the
first lines in the file. But after replacing all instances of that
character with the empty string, I still get a similar error to what I
pasted above. I manually paged through the file and found different hex
characters. It isn't practical for me to page through an entire file and
monetdb doesn't tell me which line number the problem is on.
By the way, I am using MonetDB v5.20.5.
Thanks for the help!
--
View this message in context: http://old.nabble.com/Copy-into-issues-with-mixed-ascii---hex-data-tp302389…
Sent from the monetdb-users mailing list archive at Nabble.com.
Hello, I am attempting to compile from mercurial sources. I have tried from the Oct2010_1 tag as well as tip and both error out at the same point (I ran de-bootstrap between attempts). As far as I can tell i have all prerequisites installed. Full command output is included at the end of the message. Can anyone tell me what I am doing wrong?
Thaks,
Dean
[MonetDB.hg/buildtools] (hg:default)$ hg update tip
0 files updated, 0 files merged, 0 files removed, 0 files unresolved
[MonetDB.hg/buildtools] (hg:default)$ ./bootstrap
[MonetDB.build/buildtools]$ ../MonetDB.hg/buildtools/configure --prefix=/opt/MonetDB --enable-burg --enable-mel --enable-debug=no --enable-assert=no --enable-optimize=yes
[MonetDB.build/buildtools]$ make -j4
...
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.yy.o -MD -MP -MF .deps/mel.yy.Tpo -c -o mel.yy.o mel.yy.cc
y.tab.c:178:1: warning: "MEL_MODULE" redefined
In file included from /home/duelafn/MonetDB.hg/buildtools/mel/command.h:26,
from /home/duelafn/MonetDB.hg/buildtools/mel/mel.yy:47:
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:1:1: warning: this is the location of the previous definition
y.tab.c:179:1: warning: "MEL_PRELUDE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:2:1: warning: this is the location of the previous definition
y.tab.c:180:1: warning: "MEL_EPILOGUE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:3:1: warning: this is the location of the previous definition
y.tab.c:181:1: warning: "MEL_END" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:4:1: warning: this is the location of the previous definition
y.tab.c:182:1: warning: "MEL_COMMAND" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:5:1: warning: this is the location of the previous definition
y.tab.c:183:1: warning: "MEL_OPERATOR0" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:6:1: warning: this is the location of the previous definition
y.tab.c:184:1: warning: "MEL_OPERATOR" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:7:1: warning: this is the location of the previous definition
y.tab.c:185:1: warning: "MEL_OPERATOR1" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:8:1: warning: this is the location of the previous definition
y.tab.c:186:1: warning: "MEL_FIXEDATOM" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:9:1: warning: this is the location of the previous definition
y.tab.c:187:1: warning: "MEL_ATOM" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:10:1: warning: this is the location of the previous definition
y.tab.c:188:1: warning: "MEL_USE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:11:1: warning: this is the location of the previous definition
y.tab.c:189:1: warning: "MEL_ATOMOP" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:12:1: warning: this is the location of the previous definition
y.tab.c:190:1: warning: "MEL_STRING" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:13:1: warning: this is the location of the previous definition
y.tab.c:191:1: warning: "MEL_IDENTIFIER" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:14:1: warning: this is the location of the previous definition
y.tab.c:192:1: warning: "MEL_USED" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:15:1: warning: this is the location of the previous definition
y.tab.c:193:1: warning: "MEL_NUMBER" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:16:1: warning: this is the location of the previous definition
y.tab.c:194:1: warning: "MEL_ANY" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:17:1: warning: this is the location of the previous definition
y.tab.c:195:1: warning: "MEL_BAT" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:18:1: warning: this is the location of the previous definition
y.tab.c:196:1: warning: "MEL_TYPE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:19:1: warning: this is the location of the previous definition
y.tab.c:197:1: warning: "MEL_VOID" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:20:1: warning: this is the location of the previous definition
y.tab.c:198:1: warning: "MEL_BUILTIN" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:21:1: warning: this is the location of the previous definition
y.tab.c:199:1: warning: "MEL_OBJECT" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:22:1: warning: this is the location of the previous definition
y.tab.c:200:1: warning: "MEL_VARARGS" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:23:1: warning: this is the location of the previous definition
y.tab.c:201:1: warning: "MEL_SEP" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:24:1: warning: this is the location of the previous definition
y.tab.c:202:1: warning: "MEL_ITERATOR" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:25:1: warning: this is the location of the previous definition
mv -f .deps/glue.Tpo .deps/glue.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mil.o -MD -MP -MF .deps/mil.Tpo -c -o mil.o mil.cc
y.tab.c:150: error: expected identifier before numeric constant
y.tab.c:150: error: expected ‘}’ before numeric constant
y.tab.c:150: error: expected unqualified-id before numeric constant
y.tab.c:175: error: expected declaration before ‘}’ token
make[3]: *** [mel.tab.o] Error 1
make[3]: *** Waiting for unfinished jobs....
mv -f .deps/mel.Tpo .deps/mel.Po
mv -f .deps/mil.Tpo .deps/mil.Po
mv -f .deps/mel.yy.Tpo .deps/mel.yy.Po
make[3]: Leaving directory `/home/duelafn/MonetDB.build/mel'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/duelafn/MonetDB.build/mel'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/duelafn/MonetDB.build'
make: *** [all] Error 2
FULL COMMAND OUTPUT
[MonetDB.hg/buildtools] (hg:default)$ ./bootstrap
configure.ac:24: installing `./install-sh'
configure.ac:24: installing `./missing'
Makefile.am: installing `./depcomp'
configure.ac:24: installing `./install-sh'
configure.ac:24: installing `./missing'
Makefile.am: installing `./depcomp'
configure.ac:24: installing `./install-sh'
configure.ac:24: installing `./missing'
Makefile.am: installing `./depcomp'
configure.ac:25: installing `./install-sh'
configure.ac:25: installing `./missing'
[MonetDB.build/buildtools]$ ../MonetDB.hg/buildtools/configure --prefix=/opt/MonetDB --enable-burg --enable-mel --enable-debug=no --enable-assert=no --enable-optimize=yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for python... /usr/bin/python
configure: WARNING: unrecognized options: --enable-burg, --enable-mel, --enable-debug, --enable-assert, --enable-optimize
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make sets $(MAKE)... (cached) yes
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gcc... gcc
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for lockfile... echo
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking whether ln -s works... yes
checking for rm... rm -f
checking for mv... mv -f
checking for flex version... flex 2.5.35
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for unistd.h... (cached) yes
checking for iostream... yes
checking for cstdio... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for size_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking for strchr... yes
checking for strdup... yes
checking for strrchr... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating mel_config.h
config.status: executing depfiles commands
configure: WARNING: unrecognized options: --enable-burg, --enable-mel, --enable-debug, --enable-assert, --enable-optimize
configure: creating ./config.status
config.status: creating Makefile
config.status: creating autogen/Makefile
config.status: creating conf/Makefile
config.status: creating conf/Mbootstrap
config.status: creating conf/buildtools-config
config.status: creating dummy.h
=== configuring in Mx (/home/duelafn/MonetDB.build/Mx)
configure: running /bin/bash ../../MonetDB.hg/buildtools/Mx/configure --disable-option-checking '--prefix=/opt/MonetDB' '--enable-burg' '--enable-mel' '--enable-debug=no' '--enable-assert=no' '--enable-optimize=yes' --cache-file=/dev/null --srcdir=../../MonetDB.hg/buildtools/Mx
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for bash... /bin/bash
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking getopt.h usability... yes
checking getopt.h presence... yes
checking for getopt.h... yes
checking limits.h usability... yes
checking limits.h presence... yes
checking for limits.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for unistd.h... (cached) yes
checking utime.h usability... yes
checking utime.h presence... yes
checking for utime.h... yes
checking whether stat file-mode macros are broken... no
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for ptrdiff_t... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking whether lstat correctly handles trailing slash... yes
checking whether stat accepts an empty string... no
checking for utime.h... (cached) yes
checking whether utime accepts a null argument... yes
checking for vprintf... yes
checking for _doprnt... no
checking for memset... yes
checking for mkdir... yes
checking for strchr... yes
checking for strcspn... yes
checking for strrchr... yes
checking for strstr... yes
checking for utime... yes
checking whether getopt is declared... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating mx_config.h
config.status: executing depfiles commands
=== configuring in burg (/home/duelafn/MonetDB.build/burg)
configure: running /bin/bash ../../MonetDB.hg/buildtools/burg/configure --disable-option-checking '--prefix=/opt/MonetDB' '--enable-burg' '--enable-mel' '--enable-debug=no' '--enable-assert=no' '--enable-optimize=yes' --cache-file=/dev/null --srcdir=../../MonetDB.hg/buildtools/burg
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for bison... bison -y
checking for lockfile... echo
checking for rm... rm -f
checking for mv... mv -f
checking for flex version... flex 2.5.35
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking stdbool.h usability... yes
checking stdbool.h presence... yes
checking for stdbool.h... yes
checking for stdlib.h... (cached) yes
checking for string.h... (cached) yes
checking for stdbool.h that conforms to C99... (cached) yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for size_t... yes
checking for long long... yes
checking for __int64... no
checking size of void *... 8
checking size of int... 4
checking size of long... 8
checking size of long long... 8
checking size of __int64... 0
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for memset... yes
checking for strdup... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating burg_config.h
config.status: executing depfiles commands
[MonetDB.build/buildtools]$ make -j4
(CDPATH="${ZSH_VERSION+.}:" && cd ../MonetDB.hg/buildtools && /bin/bash /home/duelafn/MonetDB.hg/buildtools/missing --run autoheader)
rm -f stamp-h1
touch ../MonetDB.hg/buildtools/dummy.h.in
cd . && /bin/bash ./config.status dummy.h
config.status: creating dummy.h
config.status: dummy.h is unchanged
/usr/bin/make all-recursive
make[1]: Entering directory `/home/duelafn/MonetDB.build'
Making all in autogen
make[2]: Entering directory `/home/duelafn/MonetDB.build/autogen'
mkdir -p /home/duelafn/MonetDB.build/autogen/autogen
cp ../../MonetDB.hg/buildtools/autogen/setup.py /home/duelafn/MonetDB.build/autogen/setup.py
cp ../../MonetDB.hg/buildtools/autogen/autogen.py /home/duelafn/MonetDB.build/autogen/autogen.py
cp ../../MonetDB.hg/buildtools/autogen/autogen/am.py /home/duelafn/MonetDB.build/autogen/autogen/am.py
cp ../../MonetDB.hg/buildtools/autogen/autogen/msc.py /home/duelafn/MonetDB.build/autogen/autogen/msc.py
cp ../../MonetDB.hg/buildtools/autogen/autogen/var.py /home/duelafn/MonetDB.build/autogen/autogen/var.py
cp ../../MonetDB.hg/buildtools/autogen/autogen/codegen.py /home/duelafn/MonetDB.build/autogen/autogen/codegen.py
cp ../../MonetDB.hg/buildtools/autogen/autogen/__init__.py /home/duelafn/MonetDB.build/autogen/autogen/__init__.py
/usr/bin/python setup.py build
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.6
creating build/lib.linux-x86_64-2.6/autogen
copying autogen/var.py -> build/lib.linux-x86_64-2.6/autogen
copying autogen/codegen.py -> build/lib.linux-x86_64-2.6/autogen
copying autogen/__init__.py -> build/lib.linux-x86_64-2.6/autogen
copying autogen/am.py -> build/lib.linux-x86_64-2.6/autogen
copying autogen/msc.py -> build/lib.linux-x86_64-2.6/autogen
running build_scripts
creating build/scripts-2.6
copying and adjusting autogen.py -> build/scripts-2.6
changing mode of build/scripts-2.6/autogen.py from 644 to 755
make[2]: Leaving directory `/home/duelafn/MonetDB.build/autogen'
Making all in Mx
make[2]: Entering directory `/home/duelafn/MonetDB.build/Mx'
(CDPATH="${ZSH_VERSION+.}:" && cd ../../MonetDB.hg/buildtools/Mx && /bin/bash /home/duelafn/MonetDB.hg/buildtools/Mx/missing --run autoheader)
rm -f stamp-h1
touch ../../MonetDB.hg/buildtools/Mx/mx_config.h.in
cd . && /bin/bash ./config.status mx_config.h
config.status: creating mx_config.h
config.status: mx_config.h is unchanged
/usr/bin/make all-am
make[3]: Entering directory `/home/duelafn/MonetDB.build/Mx'
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Mx.o -MD -MP -MF .deps/Mx.Tpo -c -o Mx.o ../../MonetDB.hg/buildtools/Mx/Mx.c
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Def.o -MD -MP -MF .deps/Def.Tpo -c -o Def.o ../../MonetDB.hg/buildtools/Mx/Def.c
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Form.o -MD -MP -MF .deps/Form.Tpo -c -o Form.o ../../MonetDB.hg/buildtools/Mx/Form.c
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Tok.o -MD -MP -MF .deps/Tok.Tpo -c -o Tok.o ../../MonetDB.hg/buildtools/Mx/Tok.c
mv -f .deps/Mx.Tpo .deps/Mx.Po
mv -f .deps/Tok.Tpo .deps/Tok.Po
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Code.o -MD -MP -MF .deps/Code.Tpo -c -o Code.o ../../MonetDB.hg/buildtools/Mx/Code.c
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Display.o -MD -MP -MF .deps/Display.Tpo -c -o Display.o ../../MonetDB.hg/buildtools/Mx/Display.c
mv -f .deps/Form.Tpo .deps/Form.Po
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Print.o -MD -MP -MF .deps/Print.Tpo -c -o Print.o ../../MonetDB.hg/buildtools/Mx/Print.c
mv -f .deps/Display.Tpo .deps/Display.Po
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Io.o -MD -MP -MF .deps/Io.Tpo -c -o Io.o ../../MonetDB.hg/buildtools/Mx/Io.c
mv -f .deps/Def.Tpo .deps/Def.Po
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT Sys.o -MD -MP -MF .deps/Sys.Tpo -c -o Sys.o ../../MonetDB.hg/buildtools/Mx/Sys.c
mv -f .deps/Print.Tpo .deps/Print.Po
gcc -DHAVE_CONFIG_H -I. -I../../MonetDB.hg/buildtools/Mx -g -O2 -MT disclaimer.o -MD -MP -MF .deps/disclaimer.Tpo -c -o disclaimer.o ../../MonetDB.hg/buildtools/Mx/disclaimer.c
mv -f .deps/Code.Tpo .deps/Code.Po
mv -f .deps/Sys.Tpo .deps/Sys.Po
mv -f .deps/disclaimer.Tpo .deps/disclaimer.Po
mv -f .deps/Io.Tpo .deps/Io.Po
gcc -g -O2 -o Mx Mx.o Def.o Form.o Tok.o Code.o Display.o Print.o Io.o Sys.o disclaimer.o
make[3]: Leaving directory `/home/duelafn/MonetDB.build/Mx'
make[2]: Leaving directory `/home/duelafn/MonetDB.build/Mx'
Making all in mel
make[2]: Entering directory `/home/duelafn/MonetDB.build/mel'
(CDPATH="${ZSH_VERSION+.}:" && cd /home/duelafn/MonetDB.hg/buildtools/mel && /bin/bash /home/duelafn/MonetDB.hg/buildtools/mel/missing --run autoheader)
rm -f stamp-h1
touch /home/duelafn/MonetDB.hg/buildtools/mel/mel_config.h.in
cd . && /bin/bash ./config.status mel_config.h
config.status: creating mel_config.h
config.status: mel_config.h is unchanged
/usr/bin/make all-am
make[3]: Entering directory `/home/duelafn/MonetDB.build/mel'
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/any_arg.mx
/home/duelafn/MonetDB.hg/buildtools/mel/any_arg.mx: ./any_arg.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/atom_arg.mx
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/atom.mx
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/atomops.mx
/home/duelafn/MonetDB.hg/buildtools/mel/atom_arg.mx: ./atom_arg.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/bat_arg.mx
/home/duelafn/MonetDB.hg/buildtools/mel/atom.mx: ./atom.cc - created
/home/duelafn/MonetDB.hg/buildtools/mel/atomops.mx: ./atomops.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/builtin.mx
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/command.mx
/home/duelafn/MonetDB.hg/buildtools/mel/bat_arg.mx: ./bat_arg.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/debug.mx
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/depend.mx
/home/duelafn/MonetDB.hg/buildtools/mel/builtin.mx: ./builtin.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/dependency.mx
/home/duelafn/MonetDB.hg/buildtools/mel/command.mx: ./command.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/epilogue.mx
/home/duelafn/MonetDB.hg/buildtools/mel/debug.mx: ./debug.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/FileInfo.mx
/home/duelafn/MonetDB.hg/buildtools/mel/depend.mx: ./depend.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/glue.mx
/home/duelafn/MonetDB.hg/buildtools/mel/dependency.mx: ./dependency.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/html.mx
/home/duelafn/MonetDB.hg/buildtools/mel/epilogue.mx: ./epilogue.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/iterator.mx
/home/duelafn/MonetDB.hg/buildtools/mel/FileInfo.mx: ./FileInfo.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/link.mx
/home/duelafn/MonetDB.hg/buildtools/mel/html.mx: ./html.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/ListIterator.mx
/home/duelafn/MonetDB.hg/buildtools/mel/iterator.mx: ./iterator.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/mel.mx
/home/duelafn/MonetDB.hg/buildtools/mel/ListIterator.mx: ./ListIterator.cc - created
echo waiting
/home/duelafn/MonetDB.hg/buildtools/mel/link.mx: ./link.cc - created
flex /home/duelafn/MonetDB.hg/buildtools/mel/mel.ll
waiting
bison -y -d /home/duelafn/MonetDB.hg/buildtools/mel/mel.yy || { rm -f waiting ; exit 1 ; }
/home/duelafn/MonetDB.hg/buildtools/mel/mel.mx: ./mel.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/mil.mx
/home/duelafn/MonetDB.hg/buildtools/mel/glue.mx: ./glue.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/module.mx
/home/duelafn/MonetDB.hg/buildtools/mel/mil.mx: ./mil.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/object.mx
/home/duelafn/MonetDB.hg/buildtools/mel/module.mx: ./module.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/operator.mx
conflicts: 32 reduce/reduce
/home/duelafn/MonetDB.hg/buildtools/mel/object.mx: ./object.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/ops.mx
/home/duelafn/MonetDB.hg/buildtools/mel/operator.mx: ./operator.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/prelude.mx
/home/duelafn/MonetDB.hg/buildtools/mel/prelude.mx: ./prelude.cc - created
/home/duelafn/MonetDB.hg/buildtools/mel/ops.mx: ./ops.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/proto.mx
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/symbol.mx
if [ -f lex.yy.c ]; then mv lex.yy.c mel.yy.cc ; fi
/home/duelafn/MonetDB.hg/buildtools/mel/proto.mx: ./proto.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/symtable.mx
/home/duelafn/MonetDB.hg/buildtools/mel/symbol.mx: ./symbol.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/type_arg.mx
mv mel.yy.cc mel.yy.cc.tmp
/home/duelafn/MonetDB.hg/buildtools/mel/symtable.mx: ./symtable.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/use.mx
/home/duelafn/MonetDB.hg/buildtools/mel/type_arg.mx: ./type_arg.cc - created
../Mx/Mx -x C /home/duelafn/MonetDB.hg/buildtools/mel/var_arg.mx
/home/duelafn/MonetDB.hg/buildtools/mel/use.mx: ./use.cc - created
echo '#include <'"mel_config.h"'>' > mel.yy.cc
grep -v '^#include.*[<"]'"mel_config.h"'[">]' mel.yy.cc.tmp >> mel.yy.cc
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT any_arg.o -MD -MP -MF .deps/any_arg.Tpo -c -o any_arg.o any_arg.cc
/home/duelafn/MonetDB.hg/buildtools/mel/var_arg.mx: ./var_arg.cc - created
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT atom_arg.o -MD -MP -MF .deps/atom_arg.Tpo -c -o atom_arg.o atom_arg.cc
rm -f mel.yy.cc.tmp
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT atom.o -MD -MP -MF .deps/atom.Tpo -c -o atom.o atom.cc
if [ -f y.tab.c ]; then mv y.tab.c mel.tab.cc ; fi
rm -f waiting
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT atomops.o -MD -MP -MF .deps/atomops.Tpo -c -o atomops.o atomops.cc
mv -f .deps/atom.Tpo .deps/atom.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT bat_arg.o -MD -MP -MF .deps/bat_arg.Tpo -c -o bat_arg.o bat_arg.cc
mv -f .deps/any_arg.Tpo .deps/any_arg.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT builtin.o -MD -MP -MF .deps/builtin.Tpo -c -o builtin.o builtin.cc
mv -f .deps/atom_arg.Tpo .deps/atom_arg.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT command.o -MD -MP -MF .deps/command.Tpo -c -o command.o command.cc
mv -f .deps/atomops.Tpo .deps/atomops.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT debug.o -MD -MP -MF .deps/debug.Tpo -c -o debug.o debug.cc
mv -f .deps/bat_arg.Tpo .deps/bat_arg.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT depend.o -MD -MP -MF .deps/depend.Tpo -c -o depend.o depend.cc
mv -f .deps/builtin.Tpo .deps/builtin.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT dependency.o -MD -MP -MF .deps/dependency.Tpo -c -o dependency.o dependency.cc
mv -f .deps/command.Tpo .deps/command.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT epilogue.o -MD -MP -MF .deps/epilogue.Tpo -c -o epilogue.o epilogue.cc
mv -f .deps/debug.Tpo .deps/debug.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT FileInfo.o -MD -MP -MF .deps/FileInfo.Tpo -c -o FileInfo.o FileInfo.cc
mv -f .deps/depend.Tpo .deps/depend.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT glue.o -MD -MP -MF .deps/glue.Tpo -c -o glue.o glue.cc
mv -f .deps/dependency.Tpo .deps/dependency.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT html.o -MD -MP -MF .deps/html.Tpo -c -o html.o html.cc
mv -f .deps/epilogue.Tpo .deps/epilogue.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT iterator.o -MD -MP -MF .deps/iterator.Tpo -c -o iterator.o iterator.cc
mv -f .deps/FileInfo.Tpo .deps/FileInfo.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT link.o -MD -MP -MF .deps/link.Tpo -c -o link.o link.cc
mv -f .deps/iterator.Tpo .deps/iterator.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT ListIterator.o -MD -MP -MF .deps/ListIterator.Tpo -c -o ListIterator.o ListIterator.cc
mv -f .deps/ListIterator.Tpo .deps/ListIterator.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.o -MD -MP -MF .deps/mel.Tpo -c -o mel.o mel.cc
mv -f .deps/html.Tpo .deps/html.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.tab.o -MD -MP -MF .deps/mel.tab.Tpo -c -o mel.tab.o mel.tab.cc
mv -f .deps/link.Tpo .deps/link.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mel.yy.o -MD -MP -MF .deps/mel.yy.Tpo -c -o mel.yy.o mel.yy.cc
y.tab.c:178:1: warning: "MEL_MODULE" redefined
In file included from /home/duelafn/MonetDB.hg/buildtools/mel/command.h:26,
from /home/duelafn/MonetDB.hg/buildtools/mel/mel.yy:47:
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:1:1: warning: this is the location of the previous definition
y.tab.c:179:1: warning: "MEL_PRELUDE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:2:1: warning: this is the location of the previous definition
y.tab.c:180:1: warning: "MEL_EPILOGUE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:3:1: warning: this is the location of the previous definition
y.tab.c:181:1: warning: "MEL_END" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:4:1: warning: this is the location of the previous definition
y.tab.c:182:1: warning: "MEL_COMMAND" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:5:1: warning: this is the location of the previous definition
y.tab.c:183:1: warning: "MEL_OPERATOR0" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:6:1: warning: this is the location of the previous definition
y.tab.c:184:1: warning: "MEL_OPERATOR" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:7:1: warning: this is the location of the previous definition
y.tab.c:185:1: warning: "MEL_OPERATOR1" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:8:1: warning: this is the location of the previous definition
y.tab.c:186:1: warning: "MEL_FIXEDATOM" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:9:1: warning: this is the location of the previous definition
y.tab.c:187:1: warning: "MEL_ATOM" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:10:1: warning: this is the location of the previous definition
y.tab.c:188:1: warning: "MEL_USE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:11:1: warning: this is the location of the previous definition
y.tab.c:189:1: warning: "MEL_ATOMOP" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:12:1: warning: this is the location of the previous definition
y.tab.c:190:1: warning: "MEL_STRING" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:13:1: warning: this is the location of the previous definition
y.tab.c:191:1: warning: "MEL_IDENTIFIER" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:14:1: warning: this is the location of the previous definition
y.tab.c:192:1: warning: "MEL_USED" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:15:1: warning: this is the location of the previous definition
y.tab.c:193:1: warning: "MEL_NUMBER" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:16:1: warning: this is the location of the previous definition
y.tab.c:194:1: warning: "MEL_ANY" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:17:1: warning: this is the location of the previous definition
y.tab.c:195:1: warning: "MEL_BAT" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:18:1: warning: this is the location of the previous definition
y.tab.c:196:1: warning: "MEL_TYPE" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:19:1: warning: this is the location of the previous definition
y.tab.c:197:1: warning: "MEL_VOID" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:20:1: warning: this is the location of the previous definition
y.tab.c:198:1: warning: "MEL_BUILTIN" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:21:1: warning: this is the location of the previous definition
y.tab.c:199:1: warning: "MEL_OBJECT" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:22:1: warning: this is the location of the previous definition
y.tab.c:200:1: warning: "MEL_VARARGS" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:23:1: warning: this is the location of the previous definition
y.tab.c:201:1: warning: "MEL_SEP" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:24:1: warning: this is the location of the previous definition
y.tab.c:202:1: warning: "MEL_ITERATOR" redefined
/home/duelafn/MonetDB.hg/buildtools/mel/mel.tab.h:25:1: warning: this is the location of the previous definition
mv -f .deps/glue.Tpo .deps/glue.Po
g++ -DHAVE_CONFIG_H -I. -I/home/duelafn/MonetDB.hg/buildtools/mel -g -MT mil.o -MD -MP -MF .deps/mil.Tpo -c -o mil.o mil.cc
y.tab.c:150: error: expected identifier before numeric constant
y.tab.c:150: error: expected ‘}’ before numeric constant
y.tab.c:150: error: expected unqualified-id before numeric constant
y.tab.c:175: error: expected declaration before ‘}’ token
make[3]: *** [mel.tab.o] Error 1
make[3]: *** Waiting for unfinished jobs....
mv -f .deps/mel.Tpo .deps/mel.Po
mv -f .deps/mil.Tpo .deps/mil.Po
mv -f .deps/mel.yy.Tpo .deps/mel.yy.Po
make[3]: Leaving directory `/home/duelafn/MonetDB.build/mel'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/home/duelafn/MonetDB.build/mel'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/duelafn/MonetDB.build'
make: *** [all] Error 2
Hello, I am still having problems compiling from sources, however, I would like to determine whether these is hope in continuing.
We have a corpus of about 18,000 documents averaging about 5000 words each. We additionally have stand-off annotations that we would like to add and query against. This totals about 300 million XML elements.
We are running 64-bit Linux with 6GiB RAM.
Database A: Loading the documents (in batches of 100) as separate collections takes about 30 min and consumes 30GiB disk space in var/MonetDB4/dbfarm.
Simple queries against database A take a long time, consume only 5% CPU and heavily work kswapd
count( for $d in pf:documents-unsafe() return doc($d)/tCorpus ) # killed after1 hour
Database B: Loading the documents (in batches of 100) into a single huge collection takes about 6 hours and consumes 120GiB disk space in var/MonetDB4/dbfarm.
Simple queries against Database B take a long time, consume only 5% CPU and heavily work pdflush
count( pf:collection("tcorpus")//tCorpus ) # killed after 3 hours
My questions:
1. Is there any hope of successfully performing non-trivial queries on either of these databases using MonetDB?
2. If so, Is loading into a single collection or separate collections likely to be preferable?
3. The above work was done using the Jun2010-SP2 SuperBall, which is the only version I have been able to compile. Has any relevant work been done since then on MonetDB4 or any of the XQuery code that might improve performance?
Thank you,
Dean
It is not October anymore, but nevertheless, the MonetDB team at
CWI/MonetDB BV is pleased to announce the Oct2010
feature release of the MonetDB suite of programs.
More information (including release notes) on this release is available
at <http://monetdb.cwi.nl/Development/Releases/Oct2010/>.
The download location is <http://dev.monetdb.org/downloads/>.
--
Sjoerd Mullender