A quick survival guide:
./configure > configure.log 2> configure.errdoes help.
rootcan help if some dependencies are installed in exotic places.
./configure --enable-allinone, this will disable some fancy but somewhat complicated dynamic
.sofile support, it can help if shared libraries are handled differently on your system than on a plain GNU/Linux box.
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:
liquidwar6binary in your
PATHenvironment variable? It might be in
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-gl1, else the game won’t run.
liquidwar6 --host, this displays informations about the host system the binary has been built for.
Now, game looks correctly installed, but you have problems running it.
$HOME/.liquidwar6/directory, you’ll find some files, the main log file
backtrace.txt. They might contain valuable information, read them. Note that while
log.csvis overwritten each time you start the game,
backtrace.txtare conserved until a new problem arises. So check the date of these files to be sure you’re analyzing the right ones. Note that byt default on Microsoft Windows
$HOME/.liquidwar6/is replaced by
C:\Documents and Settings\<username>\Liquid War 6and on Mac OS X it is in
/Users/<username>/Library/Application Support/Liquid War 6/.
liquidwar6 --defaults. This will reset all options to defaults. You might need to run this when upgrading from a version to another, since some options might appear, disappear, or defaults values can change.
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. You can also launch the game with the
--trap-errors=falseswitch, this will disable the custom popup window and allow you to get the real error.
gdb liquidwar6. Type
run --trap-errors=falseand watch output.
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-valgrindand then run it using Valgrind.
find / -type d -a -name "liquidwar6*" 2> /dev/nullto ensure you don’t have an old version of Liquid War 6 somewhere else...