After adding the updates to take my XFree86 install to 4.2.1 (binary updates), I'm getting "unresolved symbol" errors when trying to start X. Has anyone else experienced this problem? Is it a bug with the binary release (ie not releasing enough libaraies or something) or is it just me? Any ways to get around it? (apart from downloading the source, patching and recompiling)
I have attached the log output from the session. I installed the 4.2.1 update over a fresh RedHat 8.0 (Xfree86 4.2.0) install. I installed it over the top to get around a problem that caused a "floating point exception" in xvidtune. I understand this existed in the vesa driver, and was corrected in 4.2.1. Does RedHat usually customise an XFree86 release before packaging it? I don't mean a few changes in config files. I'm talking about adding / removing libraries / execs etc. This might explain why the latest XFree86 is linked to different libraries than those I have. -- +++ GMX - Mail, Messaging & more http://www.gmx.net +++ NEU: Mit GMX ins Internet. Rund um die Uhr für 1 ct/ Min. surfen!
XFree86.0.log
Description: Binary data
