[rox-users] Re: [rox-devel] Archive and pygtk notes

[Thomas L. <ta...@ec...>]

On Wed, Aug 07, 2002 at 02:52:16PM -0400, Matthew Weier O'Phinney wrote:
> 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.

It should work. Load up python and check sys.path:

	>python
	Python 2.2.1 (#1, Jul 29 2002, 23:15:49) 
	[GCC 2.95.4 20011002 (Debian prerelease)] on linux2
	Type "help", "copyright", "credits" or "license" for more
	information.
	>>> import sys
	>>> sys.path

/usr/local/lib/python2.2/site-packages should be in the list, and that is
where pygtk should have put its modules. Try running Archive from a
terminal window ('./Archive/AppRun ~/archive.tgz') and see what errors you
get...


-- 
Thomas Leonard			http://rox.sourceforge.net
ta...@ec...		ta...@us...
GPG: 9242 9807 C985 3C07 44A6  8B9A AE07 8280 59A5 3CC1