Re: [MonetDB-users] MonetSQLdb python API

On Thu, Oct 05, 2006 at 11:12:52PM +0200, Stefan Manegold wrote:

On Thu, Oct 05, 2006 at 10:31:17AM +0200, Ronald Oussoren wrote:

...

On Tuesday, October 03, 2006, at 01:22PM, Stefan Manegold wrote:

...

...

...

...

'make check' for MonetDB-4.12.1 (downloaded today) complains a lot about:

!ERROR: interpret: no matching MIL operator to 'quit()'. quit();

[...]

...

What I'm doing (on a SuSE Enterprise Linux 9 system on x86):

$ tar zxf MonetDB-4.12.1.tar.gz $ mkdir build $ cd build $ ../MonetDB-4.12.1/configure '--with-php=no' '--with-perl=no' '--with-python=/opt/python2.4/bin/python' '--with-python-incdir=/opt/python2.4/include/python2.4' '-with-python-library=/opt/python2.4/lib' '--with-python-libdir=/opt/python2.4/lib/python2.4/site-packages' '--prefix=/opt/monet-4.12.1' '--enable-debug' '--disable-optimize' $ make $ make check # -> this results in the 'quit' error mentioned earlier $ make install $ Mtest.py -r # -> works correctly

looks perfectly fine to me --- except from the make check problem --- I have to admit, though, that I never tried make check with the tar ball (only from CVS source so far) --- I'll later try it with the tar ball (from our "Daily Builds"), too...

Found it! [For the "insiders":] The problem is that with the source tarballs all .mil parts of the modules have already been extrated from the .mx files and reside readily in source tree. During `make`, they are hence(?) not copied/links to the build tree. RunMtest, however, that is used to run Mtest.py when `make check` is executed, assumes that the modules' .mil files are in the build tree (as they are in case we build from the CVS sources) and sets the monet_mod_path accordingly. Thus, Mserver cannot find the modules' .mil files, and hence no modules. There are three potential solutions: 1) We need to change the Makefiles to ensure that also with the source tarballs, `make` copies the modules' .mil files from the source tree to the build tree (and least in case they are not identical) 2) We patch configure and RumMtest.in so that RunMtest "knows" whether it use in a "from-CVS" context or a "from-tarball" context, and hence uses either builddir or srcdir, respectively, for the directories in the modpath that contain the .mil files of the modules. 3) We replicate the directories in RunMtest.in's modpath to point to both the source tree and the build tree. To be honest, I don't know right now how to do 1) or 2) quickly (and correctly), hence, I'll just try 3) --- see my checkins later tonight ... Stefan -- | Dr. Stefan Manegold | mailto:Stefan.Manegold@cwi.nl | | CWI, P.O.Box 94079 | http://www.cwi.nl/~manegold/ | | 1090 GB Amsterdam | Tel.: +31 (20) 592-4212 | | The Netherlands | Fax : +31 (20) 592-4312 |