Re: KDE3 CVS (yesterday) binaries for Woody available
-BEGIN PGP SIGNED MESSAGE- On Tuesday 29 January 2002 12:59 pm, Jens Benecke wrote: On Tue, Jan 29, 2002 at 05:36:47PM +0100, Franz Keferboeck wrote: That's simply great!! Thanx you for this... Thanks. :) I already compiled kde3 on my main computer... i didn't want to interrupt, so I had to stay awake all night, cause my computer's in the same room as my bed;-) shudder No, one of my computers (my server) is always running anyway, so I just left the other on as well (workstation, more CPU power). Took me about 8 hours to compile all of the stuff on a 1.5GHz Athlon ... ;) Your Packages are great... Thanks! Totally unrelated thought/question/request for input. Over spring break, we're looking at putting together a small cluster here in the shop. Athlon 850, dual P3 720, Duron 1 gig, Athlon 1 gig. Is it possible to use a cluster like this to compile the cvs stuff??? or am I having another flashback to the 60's? (we had better drugs then!!) :--) - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 Toll Free (866) 562-7160 Via IRC at; 205.227.115.251:6667:#OutCasts Via ICQ: UIN 138930 Failure is not an option...it's bundled with Microsoft -anonymous- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! Software is like sex. They're both better when they're free!! - Linus Torvalds As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product.
Re: KDE3 CVS (yesterday) binaries for Woody available
-BEGIN PGP SIGNED MESSAGE- On Tuesday 29 January 2002 03:00 pm, Jens Benecke wrote: On Tue, Jan 29, 2002 at 02:34:34PM -0800, G. L. `Griz' Inabnit wrote: Totally unrelated thought/question/request for input. Over spring break, we're looking at putting together a small cluster here in the shop. Athlon 850, dual P3 720, Duron 1 gig, Athlon 1 gig. Is it possible to use a cluster like this to compile the cvs stuff??? or am I having another flashback to the 60's? (we had better drugs then!!) :--) If you can get MOSIX (www.mosix.org) to run, this should be trivial. Mosix essentially makes a network of single CPU machines look like one big SMP machine. I could perhaps even join your cluster. :) But perhaps it would be easier just to share one NFS mount, compile qt-copy, kdesupport, kdelibs and kdebase on one machine, and then distribute the rest of the system on the other machines. Well, I was just thinking that if I could get mosix up and running (along with the power that it would/should allow, I could offer David or Chris access for the 'big crunch' times. (shrug) I'm not a programmer (any longer) so I would like to contribute. if I can thru pure horsepower, so much the better. :--) And yes, Jens, if you REALLY need to be part of my cluster (o! now there's a lead-in!!), yer welcome to join. :--) But first, let me GET a cluster.. Regards, good wishes, damn .conf files anyhow!! Griz - -- __ OutCast Computer Consultants of Central Oregon http://outcast-consultants.redmond.or.us [EMAIL PROTECTED] (541) 504-1388 Toll Free (866) 562-7160 Via IRC at; 205.227.115.251:6667:#OutCasts Via ICQ: UIN 138930 Failure is not an option...it's bundled with Microsoft -anonymous- Hi! I'm a .signature virus! Copy me into your ~/.signature, please! Software is like sex. They're both better when they're free!! - Linus Torvalds As a computing professional, I believe it would be unethical for me to advise, recommend, or support the use (save possibly for personal amusement) of any product that is or depends on any Microsoft product.
Re: KDE3 CVS (yesterday) binaries for Woody available
On Tue, Jan 29, 2002 at 02:34:34PM -0800, G. L. `Griz' Inabnit wrote: Totally unrelated thought/question/request for input. Over spring break, we're looking at putting together a small cluster here in the shop. Athlon 850, dual P3 720, Duron 1 gig, Athlon 1 gig. Is it possible to use a cluster like this to compile the cvs stuff??? or am I having another flashback to the 60's? (we had better drugs then!!) :--) If you can get MOSIX (www.mosix.org) to run, this should be trivial. Mosix essentially makes a network of single CPU machines look like one big SMP machine. I could perhaps even join your cluster. :) Me to;-) But perhaps it would be easier just to share one NFS mount, compile qt-copy, kdesupport, kdelibs and kdebase on one machine, and then distribute the rest of the system on the other machines. If you start make with several threads, wouldn't it be faster do do this on such a cluster - or would the network-overhead for the file-sharing make the whole thing useless? Me and some friends also consider to build a mosix-cluster (we're all in a student's hostel) - althoug they won't let me in, cause the are scared that i'll missuse it for KDE-compiling;-) -- Wenn auch die Sicherheit vor den Menschen bis zu einem gewissen Grade eintritt durch eine bestimmte Macht, Störungen zu beseitigen, und durch Reichtum, so entspringt doch die reinste Sicherheit aus der Ruhe und dem Rückzug aus der Masse. (Epikur) Me, alias Franz Keferböck GMX - Die Kommunikationsplattform im Internet. http://www.gmx.net
KDE3(beta) as unofficial add-on?
Hello, I have read the discussion about using /opt with some amusement, my opinion is like tha majority: Stay away from /opt for official debian packages. But: To have a simple solution for testing kde3 beta besides kde2 wouldn't it be good to provide unofficial debs for kde3 as long as this is called beta upstream. These unofficial packages are not part of debian and can use /opt ! This way it should be possible to have both at the same time. When kde3 matures the packages become official and replace the kde2 packages under/usr (if this isnt too much work changing the prefix in all relevant packages?) Just my 2 cent, Olaf
Why did I suggest /usr/lib/kde3 or /opt/kde3? (Re: What are Chris and Daniel actually going to do now?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 17 January 2002 00:54, Oliver Johns wrote: On Fri Dec 14, 2001 Ivan E. Moore II wrote: With kde3 my current (and yet truely tested) approach for file layout is pretty much everything under /usr/share/kde /usr/lib/kde (and /usr/lib/kde3 for the modules) /etc/kde. Any chance that Chris and Daniel will hold to that? I think my suggestion needs some clarification. What was the motivation for that? The reason is that Ivan's yet untested approach will not work well when users want to install KDE2 and KDE3 at the same time. In my approach, you can choose among KDE2 or KDE3 to your heart's content. Note that the only file conflicts will *not* happen among libraries, which is why you should install in a KDE prefix other than /usr. There are many files that conflict, from the ground up. And there is no easy solution except implementing my proposed approach. For keeping multiple versions of KDE, as agreed on by hackers on #kde (including the knows-it-all noatun developer Charles[*]), you need to install them to a specific location other than /usr. That simple. My suggestion clearly targets that. If we had only one major version of KDE at a time (which will never be the case), then there would be no need for such a change. When we have final KDE3 release, there will be a guess what: a development version which will bring the same problems over again. As of now, the decision primarily interests Chris. I ought to summarize my suggestion again: Make a /usr/lib/kde3 hierarchy. Under this hierarchy, move directories that do not belong there (according to the policy) to their appropriate locations, and symlink them in /usr/lib/kde3. /usr/lib/kde3/include - /usr/include/kde3 /usr/lib/kde3/share - /usr/share/kde3 (install manual pages to their correct locations) Add /usr/lib/kde3 to /etc/ld.so.conf That's all that is needed! Make all this with a very simple build script, and include that script in a generic debian kde package as before. Also, the proposed change does not affect any KDE2 user in anyway as it stands, so please don't be confused by what's being discussed. Regards, [*] I mean it, Charles is one guy who has wisdom. - -- Eray Ozkural (exa) [EMAIL PROTECTED] Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RgvGfAeuFodNU5wRAulRAJ9FLe9V1pfoa/f4KuYkRdWW9wch7ACfaj4d 2dm/w9uaWOzTYrZ35KrtjKo= =jNnb -END PGP SIGNATURE-
Re: Why did I suggest /usr/lib/kde3 or /opt/kde3? (Re: What are Chris and Daniel actually going to do now?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 17 January 2002 01:24, Eray Ozkural (exa) wrote: That's all that is needed! Something is left out. What do we do with binaries? I think binaries should stay in /usr/lib/kde3/bin, and linked to /usr/bin. Maybe /usr/bin/X11 would be an even better place. Would this be a good solution? Thanks, - -- Eray Ozkural (exa) [EMAIL PROTECTED] Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8RtbffAeuFodNU5wRAsZfAJ9PzfU1lm1G+/6bFvXf8F0DWLW5TACcDSYe 7WffeMs8sQuzdYFwngxUZoY= =9BjM -END PGP SIGNATURE-
Re: Why did I suggest /usr/lib/kde3 or /opt/kde3? (Re: What are Chris and Daniel actually going to do now?)
On Thu, Jan 17, 2002 at 03:51:27PM +0200, Eray Ozkural (exa) wrote: On Thursday 17 January 2002 01:24, Eray Ozkural (exa) wrote: That's all that is needed! Something is left out. What do we do with binaries? I think binaries should stay in /usr/lib/kde3/bin, and linked to /usr/bin. Maybe /usr/bin/X11 would be an even better place. Would this be a good solution? No. Your original complaint was about cluttering the namespace. With this solution, not only are you implementing TWO ugly hacks (the /usr/lib/kde3 prefix and /usr/bin symlinks), but the namespace stays cluttered. -- Daniel Stone[EMAIL PROTECTED] Zxcfb apt, karma dpkg apt dpkg has karma of 1 dpkg apt: '640K ought to be enough for anybody.' - Bill Gates, 1981 apt dpkg: bugger all, i dunno dpkg apt: The name is Baud..., James Baud apt ...but name is already something else... pgp7vW9jKZud5.pgp Description: PGP signature
Re: Why did I suggest /usr/lib/kde3 or /opt/kde3? (Re: What are Chris and Daniel actually going to do now?)
On Thursday 17 January 2002 16:10, Daniel Stone wrote: On Thu, Jan 17, 2002 at 04:57:33PM +0200, Eray Ozkural (exa) wrote: [...] I suggest you to at least implement: /usr/share/kde3 under which all KDE3 ro arch indep data should go in such as /usr/share/kde/icons. Icons are excatly the example that shows that /usr/share/kde* is the wrong thing... I have no beef with this. This is the sort of sane suggestion I wish you'd come up with more frequently. I've always thought this should be done, as /usr/share is just too cluttered. ... Please don't do this. Please keep same logical things, like icons, together. Otherwise searching for icons is a night mare. I've dirs get too crowed use subdir like /usr/share/icons/kdeX /usr/lib/kdeX That's okay but not optimal (IMO). KDE did the right thing (tm). Below icons is hi/locolor, then size subdirs. Because KDE does not care what kde package an icons comes from. In an ideal Debian system it would be the same, KDE, Gnome, fvwm ... put all their stuff together, because Debian does not care which packages includes the icons. At least that is my dream everytime the icons dialog pops up, and KDE has not the right one. If one want a view on files by package nothing can do better than the package tools. We don't need the filesystem for it. If one wants a bigger groups add eg. tags to packages so one can do apt-get update --tag kde -t unstable upgrade dpkg --tag kde -l Joe user looks for docs, icons, sounds ... Keep it together and Joe user is happy. Add good package tools and admin is happy. If both are happy you are on a Debian system ;) At least up to now. I hope it will not change. Achim [...] -- To me vi is Zen. To use vi is to practice zen. Every command is a koan. Profound to the user, unintelligible to the uninitiated. You discover truth everytime you use it. -- [EMAIL PROTECTED]
Re: Why did I suggest /usr/lib/kde3 or /opt/kde3? (Re: What are Chris and Daniel actually going to do now?)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 16 January 2002 02:24 pm, Eray Ozkural (exa) wrote: The reason is that Ivan's yet untested approach will not work well when users want to install KDE2 and KDE3 at the same time. In my approach, you can choose among KDE2 or KDE3 to your heart's content. Note that the only file conflicts will *not* happen among libraries, which is why you should install in a KDE prefix other than /usr. There are many files that conflict, from the ground up. And there is no easy solution except implementing my proposed approach. While this packaging/FHS KDE stuff is over my head, as a user and since it is being heavily air on the kde -user list I have a user comment. It seems to me that there would be only one version of KDE in Debian stable. How Debian gets to one version in stable is another matter. - -- Greg Madden -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjxHO/QACgkQaefA3q8KcpD6xgCfdO171l4+ZqQhY/72JgB6wE+f lWMAmweuFicejMFd9Nncc9Sosuqqq5Gv =LS8K -END PGP SIGNATURE-
Re: KDE3 question
On Sat, Jan 12, 2002 at 11:35:10AM +0100, Daniel Weller wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi guys, I'm trying to install KDE3 and so far everything ran well, except that I couldn't compile kdebase because configure says: checking various X settings... failed configure: error: /usr/bin/X11/xmkmf (imake) failed. Make sure you have all necessary X development packages installed. I've apt-get'd xlibs-dev, xlib6g-dev and xlibmesa-dev - and it still doesn't work. Anyone know what I've got to get? You can try apt-get install ivtools-dev and xutils those are the results apt-cache search xmkmf came up with, -John Cheers, Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8QBFjNVgxg5kyE7wRAhDiAKClLMYgFKAAQMn80PSmMTRi7NL5BwCdGOFo jNZHz+eqMO8vbuKnEs31keY= =gAJe -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: KDE3 question
On Saturday 12 January 2002 11:35, Daniel Weller wrote: Hi guys, I'm trying to install KDE3 and so far everything ran well, except that I couldn't compile kdebase because configure says: checking various X settings... failed configure: error: /usr/bin/X11/xmkmf (imake) failed. Make sure you have all necessary X development packages installed. I've apt-get'd xlibs-dev, xlib6g-dev and xlibmesa-dev - and it still doesn't work. Anyone know what I've got to get? I had same problem after upgrading Xlibs to the recent -12, I simply downgraded it to -11 and now it works again.. I would recommend awaiting a bug-fix from Brandon before upgrading X, if you use the -dev packages. -Allan
Re: KDE3 question
On Sat, Jan 12, 2002 at 01:02:33PM +0100, Allan Sandfeld Jensen wrote: On Saturday 12 January 2002 11:35, Daniel Weller wrote: Hi guys, I'm trying to install KDE3 and so far everything ran well, except that I couldn't compile kdebase because configure says: checking various X settings... failed configure: error: /usr/bin/X11/xmkmf (imake) failed. Make sure you have all necessary X development packages installed. I've apt-get'd xlibs-dev, xlib6g-dev and xlibmesa-dev - and it still doesn't work. Anyone know what I've got to get? I had same problem after upgrading Xlibs to the recent -12, I simply downgraded it to -11 and now it works again.. I would recommend awaiting a bug-fix from Brandon before upgrading X, if you use the -dev packages. Correct, he sent a message to -devel-announce about it today. -- Daniel Stone[EMAIL PROTECTED] erno hm. I've lost a machine.. literally _lost_. it responds to ping, it works completely, I just can't figure out where in my apartment it is. pgpNIwJ6NLRjJ.pgp Description: PGP signature
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Wed, Jan 09, 2002 at 07:50:48AM +1100, Daniel Stone wrote: When it's ready. Bear in mind, however, that KDE has the fastest release team/whatever known to man. Any chance of getting them to work on Debian instead/as well :-) . -- You grabbed my hand and we fell into it, like a daydream - or a fever. pgphmdjIXvPBu.pgp Description: PGP signature
testing KDE3 (was: anti-aliasing is *NOT* supported!)
I don't think AA on KDE is particularily buggy and should, instead, be considered quite an important feature if we want to eventually build a desktop UI that can seriously compete with the commercial one(s). Look feel and usability are one of the areas we are most likely to fail in and therefore requires extra attention, IMHO. It will be quite important as an interface option in KDE3, but I think Great! Now that we are on it, btw, do you know: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. + Have they announced any estimated schedule for KDE3 release on KDE mailing lists? Ie. about when can we expect official Debian packages to appear in 'unstable?' these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. :) If you say so.. - Jarno
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: It will be quite important as an interface option in KDE3, but I think Great! Now that we are on it, btw, do you know: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? + Have they announced any estimated schedule for KDE3 release on KDE mailing lists? Ie. about when can we expect official Debian packages to appear in 'unstable?' When it's ready. Bear in mind, however, that KDE has the fastest release team/whatever known to man. these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. :) If you say so.. Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) -- Daniel Stone[EMAIL PROTECTED] BenC wow...Brother is like a good company BenC I called about a problem with this printer, that I didn't even buy, and they are sending me a new drum/toner cart. free pgplJa7h2dTEY.pgp Description: PGP signature
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Wed, Jan 09, 2002 at 07:50:48AM +1100, Daniel Stone wrote: On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: It will be quite important as an interface option in KDE3, but I think Great! Now that we are on it, btw, do you know: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? I am still working with you on KDE 2.2 (remember) ;) + Have they announced any estimated schedule for KDE3 release on KDE mailing lists? Ie. about when can we expect official Debian packages to appear in 'unstable?' When it's ready. Bear in mind, however, that KDE has the fastest release team/whatever known to man. Yea, I will have to start looking at the packaging of KDE3 ASAP. these three words sum up its state in KDE2.2: buggy as shit. I don't intend to support something that is indeed buggy as shit. Live with the odd jagged pixel. :) If you say so.. Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) Sound like a plan to me. ;) Chris Cheney
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tuesday 08 January 2002 21:50, Daniel Stone wrote: On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? There was an article on DebianPlanet recently: http://www.debianplanet.org//article.php?sid=533mode=order=0thold=0 -- Regards Jeppe
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tuesday 08 January 2002 23:06, Chris Cheney wrote: :) If you say so.. Well, by all means fix it in Qt 2.2 and KDE2.2 upstream if you want. :) Sound like a plan to me. ;) Don't push me.. I just might! :P (if I knew what there is to fix, that is..) - Jarno
Re: testing KDE3 (was: anti-aliasing is *NOT* supported!)
On Tue, Jan 08, 2002 at 10:11:28PM +0100, Jeppe Buk wrote: On Tuesday 08 January 2002 21:50, Daniel Stone wrote: On Tue, Jan 08, 2002 at 10:44:13PM +0200, Jarno Elonen wrote: + How smoothly does the CVS version of KDE 3 beta coexist on the same computer with current 2.2 debian packages? I would very much like to test it already but haven't dared to install yet in the fear of making the currently fine working 2.2 unusable.. I'm not sure that it does, at all. Chris? There was an article on DebianPlanet recently: http://www.debianplanet.org//article.php?sid=533mode=order=0thold=0 Yeah, I posted that. That doesn't detail the packages themselves, BTW. Ivan may or may not have 3.0beta1 packages, I can't remember. -d -- Daniel Stone[EMAIL PROTECTED] * Tv takes a voodoo doll that looks like liiwi and stamps NM on its forehead. liiwi Tv: I'll confess nothing pgpsCinH04J8u.pgp Description: PGP signature
Re: KDE3
Yes, those packages are not ready for general use currently. AFAIK Ivan's working on them. I've experienced the same problem when I installed kdelibs4. remove them, --purge --force-all kdelibs3 and then reinstall kdelibs3. That's how you can get back to working KDE2.2. Thankfully I don't need working KDE on that machine (that's why I tried KDE3 here ;). I posted this just in case someone wants to try it. Ax -- Vaclav Hula ([EMAIL PROTECTED]) JabberID: [EMAIL PROTECTED] http://atrey.karlin.mff.cuni.cz/~ax
Re: ui_standards.rc KDE3 (Ivan?)?
On Fri, 9 Nov 2001, Ivan E. Moore II wrote: On Fri, Nov 09, 2001 at 08:32:37PM +0100, Tomas Pospisek wrote: In my ongoing quest to get kdepim to compile with Ivan's KDE3 set I've discovered that karm is looking for ui_standards.rc under: /usr/share/config/ui/ui_standards.rc as oposed to: /etc/kde3/ui/ui_standards.rc where they are by default under Debian. Now I'm unsure who is wrong. I can't find any mention of ui_standards.rc in the kdepim sources, so I guess that it's a problem with the kdelibs? most likely the problem is in how you are building kdepim or with kdepim itself. Um. Actually I stole it from you. Can you see anything wrong below: $ cat build . ./debiandirs cd kdepim ./configure $configkdepim --without-shadow --with-pam=kde --with-ldap --with-cdparanoia --with-vorbis --libdir=$kde_libdir --includedir=$kde_includedir --with-extra-includes=/usr/X11R6/include --without-ssl $ cat ./debiandirs export kde_htmldir=/usr/share/doc/kde/HTML export kde_appsdir=/usr/share/applnk export kde_icondir=/usr/share/icons export kde_sounddir=/usr/share/sounds export kde_datadir=/usr/share/apps export kde_cgidir=/usr/lib/cgi-bin export kde_locale=/usr/share/locale export kde_confdir=/etc/kde2 export kde_mimedir=/usr/share/mimelnk export kde_wallpaperdir=/usr/share/wallpapers export kde_bindir=/usr/bin export kde_servicesdir=/usr/share/services export kde_servicetypesdir=/usr/share/servicetypes export kde_includedir=/usr/include/kde export kde_libdir=/usr/lib export kde_moduledir=/usr/lib/kde2 export mandir=/usr/share/man export infodir=/usr/share/info export QTDIR=/usr/share/qt export kde_prefix=/usr export INSTALL_DATA=install -p -c -m 644 export IDL=/usr/bin/cuteidl export DCOPIDL=/usr/bin/dcopidl export DCOPIDL2CPP=/usr/bin/dcopidl2cpp export KDB2HTML=/usr/bin/kdb2html export MCOPIDL=/usr/bin/mcopidl export ARTSCCONFIG=/usr/bin/artsc-config export configkdepim=--enable-debug --with-extra-includes=/usr/include/kde3 --with-extra-includes=/usr/include/libpisock --enable-shared --disable-rpath --prefix=$kde_prefix --libexecdir=$kde_bindir --with-qt-includes=/usr/include/qt --mandir=$mandir --infodir=$infodir ? Thanks!! *t Tomas Pospisek SourcePole - Linux Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11
resolved: compiling kde3 stuff under Debian
You might remember my last request for help. So now I've made a chrooted debian installation, popped rkrusty's libqt3 package and kdebase-cvs_3.0-0.alpha1-1 fragments in it and: tpo2:rkrusty/kde3.0/source/kdebase-cvs-3.0-0.alpha1# debian/rules binary [...] checking for Qt... configure: error: Qt (= Qt 3.0.0) (libraries) not found. Please check your installation! For more details about this problem, look at the end of config.log. make: *** [build-stamp] Error 1 So aparently I'm not the only one who's got something wrong... from the config.log: configure:5510: gcc -o conftest -ansi -W -Wall -pedantic -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -g -O2 -I. -I/usr/X11R6/include -D_REENTRANT conftest.c -L/usr/X11R6/lib -ljpeg -lm 15 configure: 5550: /usr/include/jpeglib.h taking that configure:5684: checking for Qt configure: 5748: /usr/include/qt/qstyle.h taking that tried NO tried /usr/share/qt/lib tried /usr/share/qt tried /usr/lib/qt3/lib tried /usr/lib/qt3 tried /usr/lib/qt/lib tried /usr/lib/qt tried /usr/X11R6/lib tried /usr/lib tried /usr/local/qt/lib tried /usr/X11R6/lib configure:5860: rm -rf SunWS_cache; c++ -o conftest -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wbad-function-cast -Wcast-align -Wundef -Wconversion -fno-builtin -Wnon-virtual-dtor -Wno-long-long -g -O2 -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -fno-exceptions -fno-check-new -I/usr/include/qt -I. -DPIC -fPIC -DQT_THREAD_SUPPORT -D_REENTRANT -LNONE -L/usr/X11R6/lib -DPIC -fPIC -lpthread conftest.C -lqt-mt -lpng -lz -lm -ljpeg -lXext -lX11 -lSM -lICE -lresolv 15 /usr/bin/ld: cannot find -lqt-mt [...] So all the new kde packages seem to be depending on qt3-mt now :-) ! And on goes the quest. *t PS: Thanks a lot to David Bishop, Michael Ashton and Mark Hollomon for trying to help me :-) ! Tomas Pospisek SourcePole - Linux Open Source Solutions http://sourcepole.ch Elestastrasse 18, 7310 Bad Ragaz, Switzerland Tel: +41 (81) 330 77 11
Re: resolved: compiling kde3 stuff under Debian
On Thu, Oct 18, 2001 at 11:38:38PM +0200, Tomas Pospisek wrote: You might remember my last request for help. So now I've made a chrooted debian installation, popped rkrusty's libqt3 package and kdebase-cvs_3.0-0.alpha1-1 fragments in it and: tpo2:rkrusty/kde3.0/source/kdebase-cvs-3.0-0.alpha1# debian/rules binary [...] checking for Qt... configure: error: Qt (= Qt 3.0.0) (libraries) not found. Please check your installation! For more details about this problem, look at the end of config.log. make: *** [build-stamp] Error 1 So aparently I'm not the only one who's got something wrong... from the config.log: configure:5510: gcc -o conftest -ansi -W -Wall -pedantic -Wshadow -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -g -O2 -I. -I/usr/X11R6/include -D_REENTRANT conftest.c -L/usr/X11R6/lib -ljpeg -lm 15 configure: 5550: /usr/include/jpeglib.h taking that configure:5684: checking for Qt configure: 5748: /usr/include/qt/qstyle.h taking that tried NO tried /usr/share/qt/lib tried /usr/share/qt tried /usr/lib/qt3/lib tried /usr/lib/qt3 tried /usr/lib/qt/lib tried /usr/lib/qt tried /usr/X11R6/lib tried /usr/lib tried /usr/local/qt/lib tried /usr/X11R6/lib configure:5860: rm -rf SunWS_cache; c++ -o conftest -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wbad-function-cast -Wcast-align -Wundef -Wconversion -fno-builtin -Wnon-virtual-dtor -Wno-long-long -g -O2 -Wall -pedantic -W -Wpointer-arith -Wmissing-prototypes -Wwrite-strings -fno-exceptions -fno-check-new -I/usr/include/qt -I. -DPIC -fPIC -DQT_THREAD_SUPPORT -D_REENTRANT -LNONE -L/usr/X11R6/lib -DPIC -fPIC -lpthread conftest.C -lqt-mt -lpng -lz -lm -ljpeg -lXext -lX11 -lSM -lICE -lresolv 15 /usr/bin/ld: cannot find -lqt-mt [...] So all the new kde packages seem to be depending on qt3-mt now :-) ! oh yea..forgot to tell people that. :) I found out just by accident as I have it installed by default on the box I'm building kde3 stuff on...I noticed when I was looking at the deps and found libqt3-mt was listed... Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Re: kde3
future? The HEAD KDE cvs branch has moved onto qt3/kde3. There is still the 2.2 branch which is what we are using and will continue to use. 2.2.1 has just been tagged and is scheduled for release a week from Monday. That will be my next upload of any kde packages. as for qt-copy. When I get some time I'll update it. There is major changes between the old qt-copy and the current one so most of the files under the debian/ dir need to be replaced. Ivan Please stick with the 2.2.1 cvs line. KDE3 cvs not until beta2 (in sid). Maybe if you start earlier with packaging kde3 cvs stuff then please put them on some external apt source. Max
