Mserver -c $MONETDB4_PREFIX/etc/MonetDB.conf should solve the problem. apparently, Mserver does no longer automatically read $MONETDB4_PREFIX/etc/MonetDB.conf to get (a.o.) the correct monet_mod_path, and the builtin defaults are outdated: # builtin opt monet_mod_path = ${prefix}/lib64/MonetDB:${prefix}/lib64/bin see also `Mserver -d0`. IMHO, we need to either make Mserver read $MONETDB4_PREFIX/etc/MonetDB.conf, (and mserver5 $MONETDB5_PREFIX/etc/monetdb5.conf, if that isn't the case) again, or update the builtin defaults. In fact, the former has my preferences, in particular as then MonetDB[45]' configure could also add the $CLIENTS_PREFIX/lib(|64)/MonetDB/{,lib,bin} to the monet_mod_path in $MONETDB4_PREFIX/etc/MonetDB.conf resp. $MONETDB5_PREFIX/etc/monetdb5.conf, and thus make Mserver & mserv5 work out-of-the-box, again, even if clients has a different prefix than MonetDB4/5. Stefan On Tue, Jan 02, 2007 at 11:34:10AM +0100, Jan Rittinger wrote:
On 01/02/2007 11:11 AM, Fabian Groffen wrote with possible deletions:
(I assume you have the appropriate permissions to write into the default prefix, which should be /usr/local in autoconf world, but on SuSE, you never know...)
Sorry I forgot to mention that I also sourced conf/conf.bash which in my understanding sets the prefix to <dir>/<system> (in my case to e.g. /local_tmp/try_new/pathfinder/Linux).
Setting an LD_LIBRARY_PATH like this should not be necessary, as your runtime linker has this in its default path. Besides setting LD_LIBRARY_PATH is considered harmful, it also shouldn't be necessary as rpath directions are given in the compilation process.
so why does Mserver does *not* find its libraries (if I read your comment as: Mserver should now all its basic stuff)?
It looks like it cannot find the MonetDB.conf file. Have you tried --config=path/to/your/MonetDB.conf ?
I did nothing different than with my old setup. May it be that the default configuration is different with the new setup.
Trying Mserver --config=/local_tmp/try_new/MonetDB4/Linux/conf/MonetDB.conf works.
Based on these paths, I get the impression you did want to use --prefix, but didn't, hence MonetDB looking for things in the wrong place.
see my note with source conf/conf.bash above :)
Try with a right prefix, or if you don't want/need it, check why the MonetDB.conf file isn't found.
They are located in the following two directories (which is the equivalent directory as in my old setup): /local_tmp/try_new/MonetDB4/Linux/etc/MonetDB.conf /local_tmp/try_new/MonetDB4/Linux/conf/MonetDB.conf
bootstrap configure --prefix=/where/you/want/it make make install
works fine here. It might be that the default path is kind of b0rk3ned, though, so it's a good idea to set the prefix anyway.
Thanks for your advice. I just thought that MonetDB should also work (out of the box) on other circumstances where there is no common install directory (and wanted to make you aware that this is not true anymore).
Cheers, Jan
-- Jan Rittinger Database Systems Technische Universität München (Germany) http://www-db.in.tum.de/~rittinge/
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Monetdb-developers mailing list Monetdb-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-developers
-- | 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 |