> I put the page together after trying to walk thru several
> people with buggy Redhat installs. For some reason things like ldd or
> strace are not as well known to new users as they should be.
The problem here is not so much that people don't know about LDD, but that
they should not have to know about it!
ldconfig also works differently depending on its version. Sometimes the first
line in ld.so.conf is used as the first directory, sometimes the last line.
Alan and me had lots of trouble getting the install script to handle that
correctly. We now use the following to remove rouge libGLs ...
# Fix potential libGL problems
LIBGL1=`ldd $DRV_NAME/*dri.so | grep libGL.so.1 | awk -F" " '{ printf
"%s",$3 }'`
LIBGL=`echo $LIBGL1 | sed -e 's/\.1//'`
if [ "$LIBGL" != "$XF86_GL_DIR/libGL.so" ]; then
echo ""
echo -n " second copy of DRI libraries found in "
echo `echo $LIBGL1 | sed -e 's/libGL.so.1//'`
echo -n " libraries have been backed up to old.* in "
echo `echo $LIBGL1 | sed -e 's/libGL.so.1//'`
echo ""
mv $LIBGL1 `echo $LIBGL1 | sed -e 's/libGL.so.1/old.libGL.so.1/'`
mv $LIBGL `echo $LIBGL | sed -e 's/libGL.so/old.libGL.so/'`
ln -s $XF86_GL_DIR/libGL.so.1 $LIBGL1;
ln -s $XF86_GL_DIR/libGL.so $LIBGL;
fi
Kind of ugly stuff.
A newer install script (not used yet) also contains distribution specific
checks/fixes.
It might be a good idea to make a second DRI check script that just checks a
DRI installation. That could be based on the install script.
Also, Alan has been working on DRIsetup which does similiar stuff. I don't
think he has worked on it lately, but that is also a good tool to run when
you are having problems. Maybe somebody is interested in working on it some
more?
- Frank
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dri-devel
