KDE 3.4 using Konstruct

[J-Val]

I'm installing KDE 3.4 on MDK 10.1 Download, using the instructions from Mojavelinux's directions

Well the downloading of the packages goes well, there's an error occuring, and I'm don't know how to correct it. I would just post the entire log text, but the problem occurs after this....

make[6]: Leaving directory `/home/juan/tmp/konstruct/misc/pkgconfig'
        [fetch] complete for pkgconfig.
install -d cookies
 ==> Running checksum on pkgconfig-0.15.0.tar.bz2
8e3f44717a76069fcc8fdae9c252369b  download/pkgconfig-0.15.0.tar.bz2
file pkgconfig-0.15.0.tar.bz2 passes checksum test!
        [checksum] complete for pkgconfig.
install -d work
 ==> Extracting download/pkgconfig-0.15.0.tar.bz2
        [extract] complete for pkgconfig.
        [patch] complete for pkgconfig.
 ==> Running configure in work/pkgconfig-0.15.0
/bin/sh: line 1: cd: work/pkgconfig-0.15.0: No such file or directory
make[5]: *** [configure-work/pkgconfig-0.15.0/configure] Error 1
make[5]: Leaving directory `/home/juan/tmp/konstruct/misc/pkgconfig'
make[4]: *** [dep-../../misc/pkgconfig] Error 2
make[4]: Leaving directory `/home/juan/tmp/konstruct/libs/glib'
make[3]: *** [dep-../../libs/glib] Error 2
make[3]: Leaving directory `/home/juan/tmp/konstruct/libs/arts'
make[2]: *** [dep-../../libs/arts] Error 2
make[2]: Leaving directory `/home/juan/tmp/konstruct/kde/kdelibs'
make[1]: *** [dep-../../kde/kdelibs] Error 2
make[1]: Leaving directory `/home/juan/tmp/konstruct/kde/kdebase'
make: *** [dep-../../kde/kdebase] Error 2

I thought maybe somewhere some dependencies weren't linked properly, or the script has some errors....but I don't know.

I've read some people used the konstruct method and had no problems with the installation, so I'm hoping this is just a freak thing, any help would be greatful.

Thanks

[J-Val]

no ideas yet?

[Parcival]

Originally posted by J-Val
no ideas yet?

Well, the problem is that this is a rather "exotic" way of updating a software in Mandrake. Generally speaking, I have made bad experiences with installing non-RPM packages in an RPM-based distro, it's very messy.

My advice is to stick with RPMs if you want to run an RPM-based distro or run a different distro like Debian (and its flavors) or Gentoo where packages are being released in shorter intervals. However, I guess that's not the sort of help you exspected.