It''s kind of weird, since there is only one dynamic libGLU file on my harddrive (I just did a search of the whole system), and that''s /usr/X11R6/lib/libGLU.so.1.3 (there are two symlinks named /usr/X11R6/lib/libGLU.so and /usr/X11R6/lib/libGLU.so.1 that point to it).
If I specify any of those three files, or the .a variety, it will compile, link, and run. It will compile and link if I just do -L/usr/X11R6/lib/ and -lGLU, but it won''t run correctly (no video works, but everything else does, and it doesn''t crash). If I only put -lGLU it won''t link at all (can''t find the file).
It''s weird, because this problem only occurs with SDL using applications. Other ones (those using GLX) will need the -L/usr/X11R6/lib added to their Makefile, but they still run just fine.
[Resist Windows XP''s Invasive Production Activation Technology!]
. The command line I used to build it at first was something like this: "gcc -Wall ... -lGL -lGLU". It told me it couldn''t find GLU (which I obviously have), so I gave it a specific directory to look under: "gcc -Wall ... -L/usr/X11R6/lib -lGL -lGLU", and it compiled fine, but it all rendering related parts of the code didn''t do anything (clearing, flipping, drawing primitives, they all did nothing).
So, out of boredom, I eventually changed it to this: gcc -Wall ... -lGL /usr/X11R6/lib/libGLU.a" (since .a files are just a bunch of .o files, I figured, why not?). Now, it suddenly started working. Can someone explain why? I assume I''ve been linking the same libGLU.a file all along, so this is somewhat weird 
.
[Resist Windows XP''s Invasive Production Activation Technology!]
