Re: libexpat foo, was: Re: [Dri-devel] ATI radeon 9200 & DRI

[Ian R. <id...@us...>]

Keith Whitwell wrote:
> Ian Romanick wrote:
>> Michel D=C3=A4nzer wrote:
>>
>>> On Mon, 2003-11-24 at 20:01, en ne wrote:
>>>
>>>> I send you the verbose output and the ldd output.
>>>
>>>         libexpat.so.1 =3D> not found
>>
>> This is getting old.  This makes at least 10 reports of "direct=20
>> rendering not working" that turned out to be libexpat.so problems. =20
>> Are we or are we not staticly linking with libexpat for the nightly=20
>> builds?  I seriously thought that this was resolved weeks ago.
>=20
> If we're not going to link it statically, can we please use dlopen() an=
d=20
> dlsym() to get the expat functionality, and if it's not available, do=20
> nothing?

The problem seems to be with older distros that have libexpat.so.0=20
instead of libexpat.so.1.  People have found that it works if they=20
symlink libexpat.so.0 to libexpat.so.1.  Can we just link with=20
libexpat.so instead?  They dlsym option should also work, but may result=20
in other false bug reports (i.e., DRI driver ignores my settings). :(