From: Brian P. <br...@pr...> - 2000-06-15 14:02:18
|
Bill McClintock wrote: > > I've been fighting this for some time now but I have given up. > > I have written several GL apps using Mesa 3.0 and a 3dfx Voodoo2 card > and all has been going well. When 3.1 & 3.2 came out I decided to > upgrade. Well all builds ok but I don't get any output when linking to > the new libraries. > > DETAILS: > Using Mesa 3.0...make linux-glide or linux-386-glide. > Build successful. > Makes libMesaGL, libMesaGLU and libglut. > Write and make app...All works well. Hardware support and a great > frame rate. > > Using Mesa 3.1...make linux-glide or linux-386-glide. > Build successful. > Makes libGL, libGLU and libglut. > Rebuild app with the new libraries. Seems to run but no output. I > get an X frame and CPU pegs. At exit app reports a slow but not > incredibly slow frame rate. I am guessing that the hardware is setup > and call are being accepted. HMMM. Relink with old libs...works like > before. > > Using Mesa 3.2...make linux-glide or linux-386-glide. > Build successful. > Makes libGL, libGLU and libglut. > Same results as 3.1. > > I would like to use 3.2 and future releases but I just can't figure out > what is up. My code is all to the OpenGL 1.1 standard so did something > change in the init calls to Mesa? > > Anyone have any ideas? Please!!! Use ldd to be absolutely sure what you're linking with. Other than that I don't know what to say. No one else has reported a problem like this. -Brian |