Q. I am getting the error 'Invalid option -fdump-translation-unit' or
similar.
A. You need to use a version of GCC that supports this flag. Version
3.2 and newer are known to, but 3.0 and 2.95 do not. I'm not sure about
3.1. In version 4.0 the support is broken, but 4.1 fixes it.

Q. I get an error trying to move gl.c.tu, saying that the file does not
exist.
A. You are probably using GCC 4.0, which has broken support for
-fdump-translation-unit (see gcc bug 18279). Use GCC 3.x or 4.1 instead.

Q. I am getting the error "could not find GL/glext.h"
A. You need to have this file, as it defines extensions to OpenGL that
an application might use. You can obtain the latest copy from
http://www.opengl.org/registry. If you don't want to put it in your
system include directories, you can create a GL subdirectory of the
bugle source directory and put it there.

Q. I am using the NVIDIA header files, and I am getting errors about
conflicting definitions.
A. Try upgrading to the latest NVIDIA drivers. The 60 series seem to
fix many of the problems in older header files. If that doesn't help,
then see the original answer below:
A. Avoid using the NVIDIA header files. They define prototypes that do
not match the OpenGL specification, and contain other flaws as well. If
you are unwilling or unable to modify the system header files, then you
can create a GL subdirectory of your BuGLe source directory and place
alternative headers there. Mesa has good headers; try downloading the
Mesa source from www.mesa3d.org and using the headers from there.

Q. I am using Gentoo, and during compilation of bugle I get errors
similar to this one:
/usr/lib/opengl/nvidia/lib/libGLcore.so.1: undefined reference to `_nv000016gl'
A. This seems to be a problem with Gentoo's system for switching
between OpenGL drivers, that causes part of the build process to use
the X11 software drivers. A workaround is to switch to the X11 drivers
for compilation and installation of bugle:
1. Run `eselect opengl set xorg-x11' (or `opengl-update xorg-x11' on
older systems) as root.
2. Ensure that your environment is up to date e.g. `source
/etc/profile' in the shell you will use to compile bugle.
3. Unpack a fresh copy of bugle (do not use a previously configured
copy), compile and install it.
4. Switch back to the NVIDIA OpenGL driver (`eselect opengl set nvidia')

Q. I have an x86-64 (Athlon 64/Opteron/EM64T) machine with 64-bit OS,
and compilation fails with the message
/usr/lib/libGL.so: could not read symbols: File in wrong format
A. This has been reported on Fedora Core 5, where libtool incorrectly
tries to link against the 32-bit version of libGL.so. The workaround is
to run (in the build directory)
sed -i 's#sys_lib_search_path_spec="#sys_lib_search_path_spec="/usr/lib64 #' libtool
and re-run make. If this still doesn't work, see if your 64-bit
libGL.so is in a different directory and use that in place of
/usr/lib64 above.

Q. I have an x86-64 (Athlon 64/Opteron/EM64T) machine with 64-bit OS,
and BuGLe fails to work with Quake3/Doom3.
A. Quake3 and Doom3 are 32-bit apps, while you probably have a 64-bit
version of BuGLe. You will need to compile a 32-bit version. See the
FAQ for more details.

Q. I am using GL_EXT_framebuffer_object to render to texture, but the
results do not appear in the texture viewer of gldb-gui.
A. This is a known bug in NVIDIA's 76.76 driver. It is fixed in the 80
series drivers. The results should appear in the framebuffer viewer.

Q. I am using ATI drivers and when I run configure, it does not find
glBegin in -lGL.
A. I have had this reported by one Debian user, but didn't get further
details on hardware or driver version. It appears that this version
depended on but did not link to libpthread. While it is possible to
hack this in configure.ac, the same user reported other problems with
this driver, and it is probably best to upgrade to a newer driver.


For any other problems, contact me at bmerry@users.sourceforge.net. If
you are having compilation problems, then it would help to include the
generated file src/data/gl.tu, assuming compilation got that far. Be
aware that this file is generated from your OpenGL header files, and if
you are using proprietry OpenGL headers then there is a small chance
that distributing this file violates the vendor's copyright. I am not a
lawyer, so I can't give definitive advice on this.