I got it compiling. Silly me, didn’t know that the Linux console in case sensitive so a big “DOH!” and slap on the forehead for me.
Now my executable can’t find the libraries it needs; it keeps saying that libGLU.so.1 is missing - it is, but theres a symbolic link file called libGLU.so.1 that points to libGLU.so.1.2 in the X11R6/lib directory - does this need to go anywhere else?
Interestingly I deleted the link files for libGL.so.1.2, when I did this the console said it couldn’t find libGL.so.1 - but when I re-made the symbolic link from .so.1 to .so.1.2 it worked again.
SO why does it work for libGL and not for libGLU ?
“error in loading shared libraries: libGLU.so.1: Cannot open shared object file: No such file or directory.”
The symbolic linking works for libGL.so.1, so why not GLU? Could it be my versions of the library? Where did everybody get their versions from? Moreover, if they’re different can I have them?
Is there a ‘path’ like - to use the DOS analogy - that I have to set or anything? I’m getting pretty peeved now.
Right, the ld.so.conf file checked out - the paths were already in there. ‘ldconfig’ updated the cache and the program doesn’t complain about the lack of libraries anymore.
It does however crash with a seg fault and dumps the core before it does anything interesting though…
Suggestions? Maybe I should try a different version of glut and glu? Does anyone know where to download the binaries for these?
All of this should be covered in your INSTALL docs. glx is a module loaded by the X server (edit /etc/X11/XF86Config). I don’t like how you are saying that programs are seg faulting… maybe you should install your GL drivers over from scratch?
Hi there!
I suppose you are using Mesa, the free implementation of OpenGL that is widely
used by the Linux community. If that is the case, I strongly suggest you to have a look at: http://sourceforge.net/projects/mesa3d/
This is Mesa home page and there is a lot of information available. In particular, there are 4 mailling lists available, one of them is exactly for users having trouble with Mesa installation. Brian Paul himself, the author of Mesa, monitors the list and he is very helpfull!
Anyway, some simple things that you can do:
compile your code with -g option, for debugging:
cc -g program.c … -o program
Then run program to get the core. Then run
the debugger:
gdb program core
This should give you information about what went wrong. Perhaps you can post here the gdb diagnostic messages. You can run your program inside the debugger, with the command:
gdb program
To see which libraries your program really
needs, just type:
ldd program
Put your questions to the list, everyone will
try to help you!