Re: OT (a bit :) KDE cvs: klauncher crash on Debian testing
On Wednesday 13 June 2001 03:36, Christopher Molnar wrote: > Christophe Prud'homme wrote: > not want to risk messing it up. I think I'll wait a day. The cvs -D"2 > days ago" method worked for me. Don't forget to use cvs up -A next time you update kdelibs - otherwise you won't get new versions. > Whoever posted that, thanks! You're welcome > -Chris CU Andi
Re: ktip.h, kprinter.h
On Wednesday 13 June 2001 03:39, Bud Rogers wrote: > Compiling kdevelop from cvs fails because those two files are missing. They > don't seem to exist on my system. I have kdebase-dev and kdelibs-dev > installed. Anyone give me a hint what package they might be in? They are new (will be) in kdelibs-dev KDE 2.2 alpha/beta. Don't know if Ivan's 2.2alpha packages are 'recent' enough to make kdevelop (aka gideon) happy. Achim > > -- > Bud Rogers <[EMAIL PROTECTED]> http://www.sirinet.net/~budr > All things in moderation. And not too much moderation either. > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > -- 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]
Artsd does not start in kde 2.2
After upgrading to the latest version of kde 2.2, starting a kde session no longer starts artsd, the sound daemon. This is true of root as well as my user account. Where should the start command be? Charles Radding
Re: ktip.h, kprinter.h
On Wednesday 13 June 2001 07:41, Achim Bohnet wrote: > On Wednesday 13 June 2001 03:39, Bud Rogers wrote: > > Compiling kdevelop from cvs fails because those two files are missing. > > They don't seem to exist on my system. I have kdebase-dev and > > kdelibs-dev installed. Anyone give me a hint what package they might be > > in? > > They are new (will be) in kdelibs-dev KDE 2.2 alpha/beta. Don't know if > Ivan's 2.2alpha packages are 'recent' enough to make kdevelop (aka gideon) > happy. Roland Krause told me a couple of CXXFLAGS to make it work. I'll include the gist of his response in case anyone else wants to have a try. On Tuesday 12 June 2001 23:02, Roland Krause wrote: > You're not trouble, the problem is, we are in a state of flux between > KDE-2.2 and KDE-2.1.[12] right now. > Anyway, the solution is to put -DUSE_QTPRINT_SYSTEM -DUSE_KDE_2_1_1 > into your compiler options (if you compile using kdevelop). > > "Duh", you will say, if I had it I wouldnt need to compile it... > therefore you can say: > > export CXXFLAGS="-DUSE_QTPRINT_SYSTEM -DUSE_KDE_2_1_1"; ./configure > and it will also do... Adding those flags worked. I'm using Debian's build scripts, dh_make and debuild. They have their own ideas about what configure should do, etc. I had to go all the way back to admin/acinclude.m4.in to find a place the scripts didn't rewrite. If I had just exported the CXXFLAGS and run configure it would have been simpler. Anyway, I have a brand new kdevelop deb. Tonight I will play with it. -- Bud Rogers <[EMAIL PROTECTED]> http://www.sirinet.net/~budr All things in moderation. And not too much moderation either.
Re: What's happened to Brahms?
> >Brahms is actually in the official KDE sources, in the kmusic module >(which is not currently part of the official KDE release). > >http://webcvs.kde.org/cgi-bin/cvsweb.cgi/kmusic/brahms/ > >Looking at the commit dates, it seems it's being actively worked on. > >Ben. > I had a look but not knowing a lot about compiling for Debian I'm not sure how or if I can compile this for my system. I'm currently running Progeny with the Latest KDE2.1 for potato as provided by Ivan. I did try compiling the sources quite some time ago, before I had KDE. I spent many long nights compiling mico, arts and brahms but could not get anything to compile cleanly. I later fetched the old KDE1 package that Ivan put together on my request but I had problems with the midi device and then did a clean install with Progeny. How difficult would it be to fetch the latest brahms sources and compile them on my current system? I used to do quite a bit of midi writing with a realy nice Windows app called NoteWorthy Composer, which I still recommend to my Windows-using friends. I've tried RoseGarden, but it is far too old, buggy and and long over-due for the overhaul to 3.0 promised over 3 years ago! I've had mixed results with compiling app's from source. I would prefer a .deb to install to keep from cluttering up my system but know very little about how to make debs. Bruce Sass once said, If you are running testing or unstable you can package them up relatively painlessly. cd Debianize with... dh_make --custom /usr/share/doc/kdelibs-dev/dh-make ...edit a bit (scarrier than it sounds, but do read the Debian Policy Manual first, and trust that Ivan knew what he was doing when he made the template)... debuild# or "debian/rules binary", or "debian/rules" # depending on if you want to build and check # a .deb, build a .deb, or see what will be # built Hmmm, I wonder if a "back-ported" dh_make and template would work well for Potato-KDE users? but Progeny is an odd mix of potato and testing and my KDE is strictly Ivan's potato .deb's. So, I dont' know if this would work for me and if it doesn't, what packages I would need to get. It might be easier to just compile the sources and just make sure that I edit whatever I need to to be sure that everything goes in the proper place. Now that Ivan's site is back, and I can see it again, I'll have to have a good read of what he provided for making your own packages. Thanks again for all the help and for providing the latest KDE for the rest of us! Cheers, John Gay
kpackage - rpm missing dependency?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I recently installed kpackage from debian/testing. When I tried to start kpackage it crashes. I figured out that if I install rpm (which is currently only recommended) it works fine. Is this a bug or have I done anything wrong? Nikolaus Regnat -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7J/OairOupgeyXZcRAnp2AJ4jgyDVy+Td6hupkK0sqsuwcMsxeACg05Uo e7F2O0kqJgLxBI6oXkBjoKM= =HCqA -END PGP SIGNATURE-
