[PyKDE] RE: PyKDE compile error

[Xavier Spriet]

Jim,

I will need to review this further on my workstation at work but I already
know that I was running the script as root so it might not be permission
related.

I encountered this error while running an emerge pykde from gentoo so the
compile process is automated, it could therefore be a problem with the way
the ebuild was put together.

I think maybe the reason is that it tries to delete the kde 3.1.3 dcop
directory and I'm in fact using kde-cvs, that may have thrown the build
script off... I did notice a message in the script about configuring itself
for kde 3.1.3

Thanks,

Xavier 

-----Original Message-----
From: Jim Bublitz [mailto:jbublitz at nwinternet.com] 
Sent: September 8, 2003 8:43 PM
To: xavier at eliquid.com; pykde mailing list
Subject: Re: PyKDE compile error

Xavier Spriet <xavier at eliquid.com> wrote:

>  File "build.py", line 1084, in generateSource
>    shutil.rmtree(mname)
>  File "/usr/lib/python2.2/shutil.py", line 117, in rmtree
>    _build_cmdtuple(path, cmdtuples)
>  File "/usr/lib/python2.2/shutil.py", line 132, in _build_cmdtuple
>    for f in os.listdir(path):
> OSError: [Errno 2] No such file or directory: 'dcop'

> !!! ERROR: dev-python/pykde-3.7.4 failed.
> !!! Function src_compile, Line 41, Exitcode 1

build.py failed while trying to delete the dcop directory (which it tries to
do before generating a new set of C++ files for each module). Usually the
reason this happens is because you don't have write permission for either
the PyKDE-3.7-4 directory or for PyKDE-3.7-4/dcop/. It happens to me when
I've run build.py as root and then tried to re-run it as a user. Fixing
write permsissions ont he PyKDE directories (the ones created when you
untarred PyKDE) should solve it.

If that isn't the cause, let me know and I'll investigate further.

Jim