if you use the NVIDIA_GLX RPM, it auto-renames some Mesa libraries, and you might have known this already... I suggest you shutdown X, uninstall the GLX libraries, install Mesa, and rename these files to something totally ambiguous... the RPM script names them something else, like this...
The above file(s) possibly belong to a conflicting MESA rpm,
or to a previous stale NVIDIA distribution.
They have been renamed to xxx.<originalFile>.RPMSAVE to
avoid conflicting with the files contained within this
Please see the FREQUENTLY ASKED QUESTIONS section of
/usr/share/doc/NVIDIA_GLX-1.0/README for more details.
in order to know what those files are, you'd have to check the script against your install of Mesa. get the glx src.rpm from nVidia at http://download.nvidia.com/XFree86_4...-3123.src.rpm,
install it, and look in the spec (usr/src/RPMS/SPECS/NVIDIA_GLX.spec) then you reinstall your NVIDIA_GLX, and they sort of co-exist. That's ONLY if you DIDN'T use RPM to install the NVIDIA_xxxx stuff. It would be nice for you if you could use the RPM, then it's just a matter of removing GLX, installing Mesa, replacing GLX. The RPM script keeps the other non-conflicting Mesa libs more or less intact, and the configure scripts (in theory) can't tell the difference. However, if you do that, you'd have to force RPM to ignore dependencies- since the GLX RPM's require matching kernel module RPMS.
If you're using RPM already, then I just said way too much, and I forget if I was able to compile Mesa apps while this was set up... and it wouldn't mean a whole lot to you anyway, since I'm always in MDK8.2... never did Slack yet. intend to, though... i'm already a world-class slacker-- pretending to be a fifth-class hacker LOL