> I just built le last sapdb CVS on debian. Now I have a "usr" directory > with all the necessary tools. > > [EMAIL PROTECTED]:/u/tom/sources/SAP/sapdb-74$ ll usr/ [...] > I created a symlink /opt/sapdb pointing to this directory. > > I modified /usr/spool/sql/ini/SAP_DBTech.ini so that it looks > like this > : > > [EMAIL PROTECTED]:/u/tom/sources/SAP/sapdb-74$ cat > /usr/spool/sql/ini/SAP_DBTech.ini > > [Globals] > IndepData=/opt/sapdb > IndepPrograms=/opt/sapdb > > [Installations] > /opt/sapdb=7.4.4.0,/opt/sapdb > [...] > > And now dbmcli segfaults on every command. If I use my newly built > dbmcli on an old sapdb installation, it works like a charm. > Can you help > me to get it working or point me to a relevant documentation on > installing.
-1. Did you really link to /u/tom/sources/SAP/sapdb-74/usr? 0. Is the x_server running? 1. In the dev environment: $ dbmcli -s -R $INSTROOT inst_reg Your build directory should now appear in the [Installations] section again. Try executing commands with dbmcli -R $INSTROOT This should test if the problems are with the build or with accessing it as a different directory. 2. $ dbmcli -R /opt/sapdb Does this changes to the dbmcli> prompt, gives an error message or segfaults? This should test if the error happens already at the connect or later when actual commands are sent. Daniel Dittmar -- Daniel Dittmar SAP DB, SAP Labs Berlin [EMAIL PROTECTED] http://www.sapdb.org/ -- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
