Here's the errors for blargg_source.h:

[ 20%] Building CXX object source/gme/src/CMakeFiles/gme.dir/blargg_common.o
In file included from /home/jb/games/vavoom-svn/source/gme/src/blargg_common.cpp:16:0:
/hom

Made a few more corrections, please test using the latest revision.

The GME compiles fine now, thanks! The only problem I have now (and this might be exclusive to me, I don't know) is that the engine won't compile. It's still segfaulting when it's generating engine.dat. I'm running Valgrind on make with --trace-children=

You mention that when you are able to compile the engine, it doesn't runs correctly, can you run it using "-debug" parameter? This will create a debug.txt file that could indicate what's the error it's causing, which could help to find the probl

Here's debug.txt when running a straight vavoom -debug:

signal: Segmentation Violation
Log: - AddGameDir
Log: - AddGameDir
Log: - FL_Init
Log: - Host_Init
Log: Doing C_Shutdown
Log: Doing CL_Shutdown
Log: Do

Seems like the problem is in "vlumpy.exe" which is the program used to generate PK3 files for progs (which are ZIP files with renamed extension), my guess is that somehow you are using a version of zlib that is too old or isn't compiling correct

Yeah the zlib I'm using is 1.2.3. I'll try upgrading it to 1.2.5 (the latest version) and see if that helps. EDIT: Nevermind, if I force an upgrade to a newer version in Synaptic it sets it so that a whole bunch of other programs are uninstalled. Is ther

I built my own libz.so.1.2.5 and have it in a folder in my home directory. How do I change the cmake file to use the library I built (and its headers) instead of the one in /usr/lib?

You can check the cmake documentation and set the CMAKE_LIBRARY_PATH variable to the place where you have your zlib library.

Does it segfault even with the latest revision?

When using zlib 1.2.5 it still segfaults once it gets to engine.dat. This happens with both 1.33 and r4424.

Have you tried using a newer version of GCC? It could help to solve your problem.

I'm using GCC 4.5.3.

I'll close this thread, since the main problem reported has been fixed, if you have more details about this, post them in the segfault thread.