Next: How to play, Previous: Installation, Up: User's manual
A quick survival guide:
./configure.
/etc/ld.so.conf and running ldconfig as root
can help if some dependencies are installed in exotic places.
CFLAGS, LDFLAGS and LD_LIBRARY_PATH.
If none of these help, consider reporting a bug, or search the mailing-lists for help.
Here's a check-list to ensure that your installation is correct:
make install?
liquidwar6 binary in your PATH?
It might be in /usr/games.
liquidwar6 --pedigree. Look at the output. Check the
compilation date & time, the prefix, the version number.
liquidwar6 --show-map-dir and liquidwar6 --show-mod-dir.
What does it show? Are these absolute paths? Do they exist? What's there?
Normally, they should be paths which contain the version number, and
be populated with sub-directories and files.
Now, game looks correctly installed, but you have problems running it.
liquidwar6 --defaults. This will reset all options to defaults.
liquidwar6 --test. This should run a complete test suite, many functions in the game will be tested automatically, and errors reported.
liquidwar6 --show-script-file. Are you really running the right code?
make uninstall && make clean && make && make install.
Many problems can come from using a wrong shared module,
especially with beta versions.
gdb liquidwar6. Type run and watch output.
stdout or stderr.
You can change this
by modifying some environment variables: export LD_DEBUG=all.
This is very verbose but does help finding bugs.
./configure --enable-valgrind and
then run it using Valgrind.
$HOME/.liquidwar6/ directory, you'll find two files, log.csv and dump.txt. They might contain valuable information, read them.
find / -type d -a -name "liquidwar6*" 2> /dev/null to ensure you don't
have an old version of Liquid War 6 somewhere else...