From: Matthew W. O'P. <wei...@gr...> - 2002-08-07 18:51:59
|
I grabbed the tarballs for Archive, ROX-Lib2, and pygtk from the rox website recently, installed ROX-Lib2, compiled and installed pygtk using a prefix of /usr/local (which is in my LD path), and went happily on my way. I tried un-archiving a couple of tarballs that day, and everything was hunky dory. After an interval of a day or two (and several reboots), I had an actual use for Archive, and went to decompress a tarball... to the sight of no dialogs... Ignoring it, I went into a terminal and did it manually. I got to thinking about it today, and realized that I'd had a similar problem with my gtk2 theme engines a couple days ago... I use a Debian (sid) system, and I discovered the hard way that I had to compile the gtk2 theme engines using the same prefix with which gtk2 was compiled, i.e. /usr. On Debian, any binaries for the distribution are compiled with the /usr prefix. So I uninstalled pygtk, recompiled with prefix=/usr, installed -- and voila! it worked fine. It might be handy to note in the Archive FAQ that pygtk needs to be compiled in the same prefix as python and/or gtk2 -- simply compiling to a prefix in the LD path won't work. --Matthew |