KDE-Forum.org

Qt gets configured to use the system libjpeg, so install the libjpeg62-devel package.

You always need the corresponding *-devel package if there is anyone, so install libpcre0-devel*.rpm.

You can try to install the development packages of your current KDE version (kdebase-devel) and your package manager will likely install most necessary dependencies automatically.

I'm not sure that you even need the tiff development packages to use konstruct, as i remember - i had the same problem and installed the vanilla tiff files and it worked .

Hope it works for you
Seb

Hi,

I think what Seb meant was to get the source for tiff ( http://www.libtiff.org/ ) and compiling it. Vanilla = source from the author, not from the distributor, ie. vanilla Linux kernel from http://www.kernel.org vs. kernel from the distributor. Distributors packages might have some minor modifications on them or there could be patches that aren't in the vanilla sources.
If I am completely clueless what I am talking about, please someone set me straight.

Quoted

I'm getting frustrated, I have encountered half a dozen lost dependencies/missing packets that were required - and I'm getting tired. Like I said I'm new in Linux, and the way the thing goes - I'm gonna stay a newbie (aka.return to Windows) ... I only can imagine what was (and still is) it like when there weren't such wonderful Linux GUI's that did much of the job, so automated... still IMHO, there are far away from a Mac/Microsoft OS [not trying to start a flame here, just a poor user's opinion]..

If you are all new to Linux I would recommend NOT to compile your programs from the source, you should wait until your distro has prepared proper packages for you. And if you want to learn how to compile your programs by yourself, I would recommend to start with something little bit smaller and not so complicated as KDE. IMHO konstruckt is NOT a newbie tool.

And if you are comparing program installation in Linux with a Mac/Windows, please do remember that you aren't compiling programs from the source to Mac/Windows (well at least most of the users aren't), you are installing binaries just like in linux when you install *.rpm. I think if you try to compile programs for Mac/Windows you probably find out that there are dependencies there also (I really don't know what I am talking about, just assuming since I have never ever compiled anything on Mac/Windows).

Anyway, IMHO normal users who aren't that much interested in computers shouldn't have to compile programs them self, it is a distributors job to do that. But if you want to compile programs, be ready for problems on the way.

ps. If you want to know about some of the dependencies in KDE here is some information about that http://www.se.linuxfromscratch.org/blfs/view/cvs/kde/kde.html , there is also a lot of information about the compiling.

Quoted

Well, I seem to hit a nerve, didn't I? My intention from the start wasn't to make compilation - just to upgrade from KDE 3.1 to KDE 3.2.2 via an "automatic" way/process - at least that is what Konstruct is promising...

Don't get me wrong, konstruct is a fine tool, but if they are promising that konstruct is an easy and automatic way to upgrade your KDE, my opinion is that they a little bit misleading. IMHO konstruct is very good at testing new versions of KDE without losing your working KDE and it does automate the compiling process, as long as everything works out allright and if it doesn't work, there is no point for automation . Also I wouldn't call it a proper upgrade because it puts everything on your home directory, not where everything actually belongs (where that is, is a matter of another discussion .
I am not saying that people who make konstruct are doing a bad job because it doesn't work everywhere, there is just too much different kind of linux installations for it to work on all of them.
About compiling stuff and Mac/Windows, I was trying to say that when people are used to do some things one way they might find another way to do it annoying. For example I have used win98 few times lately(long story, don't ask) and everything seems to work, but at the same time it doesn't feel to work like it supposed to, that is, the way like I am used to. And that is annoying.

Quoted

I'm very interested in computers and - beilieve me - I'm not so stupid to try something out of my knowledge (and quite complicated as it turned out) as KDE installation, but I was fooled by thinking that Konstruct would install all the needed files by itself

Yes I can see that you are interested in computers, otherwise you wouldn't try to use konstruct and if you are preferring a part where I said that normal users shouldn't compile their own programs I wasn't preferring to you personally as a normal user, I meant the mystical "Joe Average".
You are already beyond average user because you are trying to compile KDE and not only trying, but also finding out how to do it and not giving it up . It IS NOT something that one can't learn, allmost everybody can, look at me, even I learned how to do it eventually. So after you have done your KDE installation it will be a lot easier to install any other program from the source, but I still would say that it is easier to start learning how to do your own compiling from a little application than from the programs like KDE. But you have to start somewhere, right?

Quoted

Anyway now I'm in the middle of it, and I want to complete it.. that's all.
Thanks for the input anyway, I'll surely visit the http://www.se.linuxfromscratch.org/blfs/view/cvs/kde/kde.html as I want to learn more of the compilation process, although I'll try to finish first KDE upgrade (cross my fingers.. )

I hope that you get you problems solved and a shiny new KDE installation up front of you. My fingers are crossed for you.