> > The only thing I can think of to try now is making sure your system is > > actually using the version of libGL that you built and not the system > > one using the following command. > > > > ldconfig -p | grep libGL.so > > > > The libGL that you built should be at the top of the list. > > I've got it! > Tim, your hint drove me in the right direction. > > For several years I only had to put r600_dri.so into the 'old' (distro) > update path /usr/lib/dri/updates/ to get current Mesa code running. > > But after your 'bad' commit > fb78fa58d2a60110bfd428ca8d41b746b69b6724 > (mesa: make ARB_debug_output functions an alias of KHR_debug) > > I have to copy libGL.so.1.2.0 from the Mesa git tree to > /usr/local/lib/ > AND replace /usr/lib/dri/r600_dri.so > to get /opt/ogl-samples> ./build/release/gl-320-primitive-sprite > running.
Well my commit is not really 'bad' but it seems your method of updating is. For a correct way to update things and not blow away your system libs (just use config files instead) you should read this: http://www.x.org/wiki/radeonBuildHowTo/ Your update procedure probably explains all the other warning messages you are getting too. > What's really weird I ONLY have to do this for ogl-samples... > ...all other (tested) apps works the 'old' way. > Yes, they throw the MESA_DEBUG warnings, but works: It works but not updating libGL means you probably wouldn't have been getting access to new extensions after upgrading anyway. The reason ogl-samples doesn't work and others do is normal applications wouldn't be using the debugging extensions so you wouldn't have hit the problem. And when I say problem I mean the problem of mixing incompatible libs. _______________________________________________ mesa-dev mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/mesa-dev
