Christian Veit wrote:
Hallo,
you don't need to hack the code to define that, just use the configure script (look ./configure --help for all options) there should be an option for ieee1394 or dv or something like that ...
I've installed Gem with apt-get install before so i don't have to use the
so you are on debian ?
./configure script before. I've tried to use it by typing
./configure --with-ieee1394
but there is something wrong with opengl
loading cache ./config.cache HEAD: /usr/include /usr/local/include ../../../GemLibs/
checking for X... no checking for MMX... checking MMX found... checking for main in -lX11... no checking for main in -lXext... no checking for XF86VidModeGetAllModeLines in -lXxf86vm... no
you will need the X development (xlibs-dev) libraries
if you are running etch/sid you also need to install the libxxf86vm-dev package.
checking for sin in -lm... yes checking for main in -lz... no checking for glInitNames in -lGL... yes checking for gluLookAt in -lGLU... no checking for gluLookAt in -lMesaGLU... no incomplete OpenGL (no GLU)
What is GLU and how can i make it run? In the ./config help i didn't find anything about that.
well, the README.build file says, that the prerequisites are (among others) "openGL + GLU" and it gives a link to the mesa homepage.
the first hit on http://www.google.at/search?q=opengl+glu gives me "GLU is the OpenGL Utility Library"; you have to install it (and also its dev-package).
basically, for each package that is needed by Gem you also have to install the dev-package (since you are compiling)
mfg.asdr IOhannes