PyKDE build problems [was: Re: [PyKDE] PyKDE with KDE 3.0.1?]

[John J. Lee]

Knowing, thanks to Ricardo's post yesterday, how to fool PyKDE into
thinking KDE 3.0.1 is 3.0.0, I tried rebuilding it.  I wiped PyKDE, and
unpacked clean from the same source package I used before, used the same
configure command from my shell history, but this time, unlike last time
where it complained about the KDE version, it tripped over itself (this
is before any modification of ckversion.py):

$ ./configure --with-qt-dir=/usr/al/bin/python2.2 --with-kde-dir=/usr/local/kde --with-pyqt-sip-dir=../PyQt-3.2.4/sip
[...]
config.status: creating config.h
checking for -lz... /usr/lib
checking for -ltiff... /usr/lib
configure: creating ./config.status
config.status: creating Makefile
sed: file /tmp/cs4026-465250833/subs-2.sed line 47: Unterminated `s' command
config.status: creating dcop/Makefile
sed: file /tmp/cs4026-465250833/subs-2.sed line 47: Unterminated `s' command
config.status: creating kdecore/Makefile
sed: file /tmp/cs4026-465250833/subs-2.sed line 47: Unterminated `s' command
config.status: creating kdesu/Makefile
sed: file /tmp/cs4026-465250833/subs-2.sed line 47: Unterminated `s' command
config.status: creating kdefx/Makefile
sed: file /tmp/cs4026-465250833/subs-2.sed line 47: Unterminated `s' command
config.status: creating kdeui/Makefile
sed: file /tmp/cs4026-465250833/subs-2.sed line 47: Unterminated `s' command
config.status: creating kio/Makefile
[...for reasons of its own, konsole refuses to copy following lines, but
it's just more of the same sed errors...]
config.status: creating config.h
config.status: executing depfiles commands

Usage:

  build -q <Qt version> -k <KDE version> -p <PyQt/sip path>

  build --qt <Qt version> --kde <KDE version> --path <PyQt/sip path>

           -or-

  build -m <module name>

  build --module <module name>

Traceback (most recent call last):
  File "./build", line 481, in ?
    if haveMod:
NameError: global name 'haveMod' is not defined


I can't imagine what I might have changed in my system configuration that
could affect this, but anyway, it certainly looks like a build bug.  It
seems whatever created the temp sed files diligently deleted them again,
so I can't post them.


John