next up previous contents
Next: Node Documentation Up: Overflow User's Manual Previous: Compiling and Installing   Contents

Subsections

Troubleshooting

1) The binary distribution I downloaded crashes on startup

There can be many causes of that. The most common is that you have a different libstdc++ than the one Overflow was compiled with. Another cause could be that you have FFTW compiled without -enable-float, while Overflow was linked with a float version of FFTW. Overflow has no way to detect that so it crashes. In both cases, the best thing to do is to build Overflow yourself.

2) I compiled Overflow myself and it crashes on startup

The main cause for this is a bug/missing feature in libtool that prevents it from working correctly with C++ on some platforms. This happens mostly on non-Linux platforms though not always. If you suspect that's your problem, try running configure with the -libtool-ld=g++ option.

3) Overflow tells me it cannot find libflow.so

This can happen if you compile Overflow and then move the installation directory (It can sometimes happen for other reasons). You can set the LD_LIBRARY_PATH to <overflow install dir>/lib. Note that if you moved the Overflow directory, you'll also need to set VFLOW_HOME.

4) The ``New Node'' menu is empty

You probably moved the Overflow install directory, see 3). Another possibility is if you compiled with -enable-static flag. Because Overflow toolboxes are dynamically loaded, everything must be compiled as shared libraries (which is the default in configure).

5) Overflow doesn't compile on my box

First, make sure you have the latest release version. If it doesn't work, you should try the CVS version. If it fails too, please contact us and we'll do our best to make Overflow compile on your platforms.

6) I downloaded a more recent version and it doesn't even compile

This can be due to the fact that you installed an earlier version (0.5.0 and earlier) in a path like /usr or /usr/local. The problem is that the old Overflow includes ended up somewhere like /usr/include so when you try compiling a newer version, g++ sees the old includes (because they are in the include path) instead of the new ones.


next up previous contents
Next: Node Documentation Up: Overflow User's Manual Previous: Compiling and Installing   Contents
Jean-Marc Valin 2002-06-17