Bugs item #1677357, was opened at 2007-03-09 16:33 Message generated for change (Comment added) made by sjoerd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1677357&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Build Group: MonetDB5 5.0_beta1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Sjoerd Mullender (sjoerd) Assigned to: Niels Nes (nielsnes) Summary: mserver5 with sql from RPM doesn't run Initial Comment: I'm not sure which category and group to place this in, nor who to assign it to... I installed the MonetDB-SQL-server5 RPM from the nightly builds together with the packages that resolve the dependencies on a clean 64 bit Fedora Core 6 system. I can start mserver5 with no problem (but only as root), but when I type in include sql; I get a list of errors. The start of the list is important: >include sql; #WARNING: LoaderException:loadLibrary:sql: loader error lib_logger.so.0: cannot open shared object file: No such file or directory #WARNING: LoaderException:loadLibrary:sql: loader error lib_logger.so.0: cannot open shared object file: No such file or directory !MALException:MAL.getAddress:address of 'sql.SQLsession' not found [ more MALExceptions deleted ] When I strace this, I see that /usr/lib64/MonetDB5/lib/lib_sql.so gets opened (after a false try of /usr/lib64/MonetDB5/lib_sql.so), and then there are attempts to open various other .so which all fail. The paths tried are mostly somewhere under /scratch/monet.GNU.64.64.d.14411/MonetDB5/.GNU.64.64.d-Fedora6 which of course isn't going to work on a clean system. My feeling the problem lies in libtool. When looking at the rpmbuild output in the test web, I see that libtool is called with -rpath /usr/lib64/MonetDB5/lib, but libtool then calls gcc with a completely different -rpath. Interesting is that I don't get the equivalent problem using MonetDB4 + SQL from RPM. It also tries to open the .so's under /scratch/*, but it then continues with opening .mil files which in turn open .so's from the correct location. ---------------------------------------------------------------------- >Comment By: Sjoerd Mullender (sjoerd) Date: 2007-03-12 18:03 Message: Logged In: YES user_id=43607 Originator: YES After some more investigating I come to the following conclusion. When the RPM is built, libtool does relink the .so's to contain the paths of dependent .so's. But since dependent .so's from other MonetDB projects are not installed properly (i.e. MonetDB5 is not installed from the just built RPM when sql is being built), the dependent .so's paths are not their final paths (/usr/lib*/MonetDB?/lib) but a temporary path (/scratch/...). The reason that MonetDB4/SQL does work is most likely because dependent .so's are loaded explicitly through MIL code before the .so itself is loaded. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=1677357&group_id=56967 ------------------------------------------------------------------------- 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-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
