This has already been discussed in length in bug 204600.
SDL-1.2.10 no longer links directly against libX11.so.6 but instead dlopen's it
when needed. The idea behind this is to be able to use SDL apps on the
framebuffer (for example) without having to install libX11 on the system.
This new way of doing things is working fine on i386 and pcc, but for some
reason SDL on x86_64 still directly links to libX11.so.6 (and friends).
On x86_64 :
# rpm -q SDL
# ldd /usr/lib64/libSDL.so
libm.so.6 => /lib64/libm.so.6 (0x0000002a957f9000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000002a95a7c000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x0000002a95c80000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x0000002a95f8c000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x0000002a9619d000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x0000002a963a0000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000002a965aa000)
libc.so.6 => /lib64/libc.so.6 (0x0000002a967c4000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x0000002a96b11000)
libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x0000002a96d14000)
But on i386 :
# rpm -q SDL
# ldd /usr/lib/libSDL.so
linux-gate.so.1 => (0xffffe000)
libm.so.6 => /lib/libm.so.6 (0xf7f29000)
libdl.so.2 => /lib/libdl.so.2 (0xf7f25000)
libpthread.so.0 => /lib/libpthread.so.0 (0xf7f0e000)
libc.so.6 => /lib/libc.so.6 (0xf7dd1000)
This is not a big impact bug, but should be fixed non the less. Especially SDL
should be consistent across all architectures. The current inconsistency leads
to weird ununderstandable bugs like 204594, 204600 and I've hit a similar bug
when rebuilding a package for that other repo (which has lead me to further
investigating this with the above conclusion).
Hmm, strange your modifications in 1.2.10-6.2 should have fixed this, but the
problem is still there in 1.2.10-9 however rebuilding 1.2.10-9 from the srpm
outside of mock fixes this, maybe a missing BuildRequires?
Or maybe a problem elsewhere which has been fixed in the meanwhile?
Fixed in rawhide in package SDL-1.2.11-2 or newer.