On 3/23/07, Randy McMurchy <[EMAIL PROTECTED]> wrote: > Dan Nicholson wrote these words on 03/23/07 19:39 CST: > > > But that wouldn't solve this problem since libX11 doesn't live in > > /opt/xorg/lib/X11. Now I'm looking at the Python sources and I see > > that they're just guessing a sample of hardcoded paths and don't look > > in /opt/xorg. Try this: > > > > sed -i 's%/usr/X11R6%/opt/xorg%' setup.py > > > > before building python. > > How about providing a /usr/X11R6 symlink pointing to the Xorg > installation until such time we feel comfortable without it?
I'm no fan of compatibility symlinks, but I suppose this is probably needed for a few corner cases. I'd still like to fix this Python case, though, since we know about the breakage. > [EMAIL PROTECTED]: ~/build > ls -l /usr/X11R6 > lrwxrwxrwx 1 root root 5 Mar 12 22:00 /usr/X11R6 -> X11R7 > > I know, old school. But it works. The method in the book doesn't. :-( Most of the time it does, but I suppose there are only so many random places a script can guess that you've installed X. Actually, I guess I think this because I have X in /usr, so it's very rare that things break. So, I guess it should say something like "If you didn't install X to /usr/X11R6 or /usr, create a symlink to ensure your system is compatible with other X related software:" ln -sv $X_PREFIX /usr/X11R6 Since you'd just have a never ending symlink train if you tried to link /usr/X11R6 -> /usr. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
