How-To and FAQ

• Q: Using automake I get an error message "directory should not contain /" - what can I do?

A: Probably you have an outdated automake version installed, we have seen such problems with 1.7.9. Upgrade to at least 1.10.1.

• Q: While installing rasdaman I find out, during ./configure, that some further packages are required. Can you give a summary of these?

A: Besides the standard ones which should be available on any vanilla Linux, it is this list: g++, make, git-core, autoconf, libtool, gawk, flex, bison, ​libreadline-dev, ​postgresql 8.3.x, ​libecpg-dev, ​sun-java6-jdk, libtiff-dev, libjpeg-dev, ​libhdf4g-dev, ​libpng12-dev, ​libnetpbm10-dev, libopenssl-devel.

• Q: Having done all the above, ./configure complains about missing curses although ncurses is there.

A: You have run into a ​bug in the ncurses package; in /usr/lib, manually create symlinks libcurses.a → libncurses.a and libcurses.so → libncurses.so.

• Q: configure complains that some required files, like install-sh, cannot be found.

A: retry ./configure after running

automake --add-missing

• Q: I get a link error, function ECPGget_connection cannot be found.

A: What appears to have happened is that in PostgreSQL 8.3.0 they removed ECPGget_connection and they have reintroduced it by 8.3.7. So PostgreSQL versions 8.3.0 up to (but excluding) 8.3.7 cannot be used.

• Q: I get C++ compilation errors.

A: Make sure you use the proper compiler version (see [Requirements]). GNU folks have a relaxed view on backwards compatibility even with minor release changes, and we have experienced such problems indeed.

• Q: When running the script "create_db.sh", I get the following cryptic error message: Creating base RASBASE…Warning/error in AdminIf Connect: SQLSTATE: 08001 SQLCODE: -402

A: There are several possible reasons:

Execution permissions. Run the script as the user owning the postgresql processes. Use only that user for further work with rasdaman (see Installation Guide). If you use Ubuntu and installed postgres with apt-get, then you should probably login as user postgres. (The postgres db does not allow full access to rasdaman tools, because they do not run under the administrative user that launched the db server process.)

Blocked incoming connections. Another cause of the problem might be that postgres does not allow incoming connections. If you have Postgres v8 or more recent, modify file "postgresl.conf" and set (uncomment) the option

listen_addresses = 'localhost'

TCP-IP connection. If you have Postgres v7, set (uncomment) the following option:

tcpip_socket = true