Next: How to play, Previous: Installation, Up: User's manual
./configure
. Running ./configure > configure.log 2> configure.err
does help.
/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
? make check
?
liquidwar6
binary in your PATH
environment variable?
It might be in /usr/games
.
liquidwar6 --pedigree
. Look at the output. Check the
compilation date & time, the version number.
liquidwar6 --audit
. What do these paths look like?
Are they absolute paths? Do they exist? What's there?
Normally, once the game is installed, all of them should exist,
and be populated with sub-directories and files.
liquidwar6 --modules
, to know which modules where compiled.
You need at least one graphical module, for instance mod-gl
,
else the game won't run.
Now, game looks correctly installed, but you have problems running it.
$HOME/.liquidwar6/
directory, you'll find two files, log.csv
and dump.txt
. They might contain valuable information, read them.
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.
find / -type d -a -name "liquidwar6*" 2> /dev/null
to ensure you don't
have an old version of Liquid War 6 somewhere else...