I'm building the KDE port on OpenBSD 2.8 and it is taking forever
to build kernel/qrichtext.o in the qt2 port. Is this normal or
do I need to change anything?
Eric Johnson
Eric Johnson
> Eric Johnson
Or upgrade to a 1.0GHz Athlon with 256MB minimum :-)
>> I'm building the KDE port on OpenBSD 2.8 and it is taking forever
>> to build kernel/qrichtext.o in the qt2 port. Is this normal or
>> do I need to change anything?
>> Eric Johnson
>Some of those c++ sources do seem to take forever. Use a different xterm
>or console and run top to see what's happening.
>Or upgrade to a 1.0GHz Athlon with 256MB minimum :-)
--
David Terrell | "Instead of plodding through the equivalent of
Prime Minister, NebCorp | literary Xanax, the pregeeks go for sci-fi and
http://wwn.nebcorp.com | http://www.monkeybagel.com/ "Origins of Sysadmins"
That kind of takes the fun out of it. But I'll try it and see
what happens.
Eric Johnson
last time i tried this -- about two weeks ago -- it took two and a half daysQuote:>I'm building the KDE port on OpenBSD 2.8 and it is taking forever
cp
Two and a half days!
Hmmm. I might as well kill the job now.
I did take advantage of the delay this afternoon to go
get a haircut. So it wasn't a complete waste of time.
By the way, I tried using the packages, but it seems to me
that it was mixing up multiple versions and wouldn't run at all.
Eric Johnson
That must have been a bit underpowered. I went ahead and let it
finish and it took less than 24 hours on mine. I'm not sure how
much left because it was still running when I went to sleep after
midnight and it was finished when I woke up.
I haven't tried it out yet. I hope it works.
Eric Johnson
Quote:> Or just install the precompiled binaries.
That makes no sense.Quote:>I wonder if it is possible to compile OpenBSD binaries on another platform,
>such as Linux...? Anyone?
1. Building KDE 2.0 with KDE 1.1.x active...
I've tracked down the problem taht I've been having trying to build off
the KDE 2.0 line (using cvsup to download) to one sequence, which
probably isn't that uncommon:
1) I'm currently running KDE 1.1.2, which is what is installed in my
/usr/lib and /usr/include directories.
2) I'm trying to build KDE 2.0 in this environment.
3) The configure scripts put /usr/include as the $kde_include directive.
4) The configure scripts put $kde_include as the first thing for the
makefiles to include.
5) This causes, when building, things like:
#include <qt*.h>
#include <k*.h>
to load the 1.1.x versions in /usr/include, not hte ones that I've built
out of qt-copy and kdelibs.
This doesn't compile.
If I hack up the makefiles in question to load /usr/include AFTER the
local versions then I'm all ready and set to go. However, I'm sure there
is a way to do this within the configure scripts (but I haven't found
out how to do it).
As a small point, my first configures were done without QTDIR and
KDEDIR set. I've set those environment variables now and I'm trying
again.
If someone knows how to accomplish this, I'd greatly appreciate a reply!
Thanks in advance,
Kirk Wylie
2. multiple-device driver (MD): performance?
5. Building kde 3.1 with konstruct
6. Info: Working third party PCI Cards under AIX
7. problem building kde-1.1.1 from src
9. Trouble building KDE 1.1.2 as well :-(
10. libbfd.so problem while building kde
11. Building KDE
13. Building KDE 1.1 on Solaris x86 - please help