[Turnpike]

I installed KDE from Fink and everything appears to be running quite wonderfully. However, I have been unable to find any binaries for Koffice online, and it doesn't appear to be on Fink. Is there any way to run this program through Apple's X11 and KDE? I'd rather do something that doesn't involve compiling, as my Sawtooth (400) isn't exactly a powerhouse these days.

Also, if there is any good repository of KDE apps that would work well with my setup, could somebody please point me in the right direction?

Thanks.

[afphreak01]

fink does have koffice packages... i never tested them, but heres a search i did off fink.sf.net

maybe you need to update fink?

[Turnpike]

ahh, okay... the problem was that Fink doesn't search the unstable tree by default, and koffice is there. Some modification to fink.conf should fix the problem. Thanks.

[wataru]

FinkCommander is a great GUI for fink. You can enable the unstable tree very easily from there.

[gitbox]

Originally posted by Turnpike:
I installed KDE from Fink and everything appears to be running quite wonderfully. However, I have been unable to find any binaries for Koffice online, and it doesn't appear to be on Fink. Is there any way to run this program through Apple's X11 and KDE? I'd rather do something that doesn't involve compiling, as my Sawtooth (400) isn't exactly a powerhouse these days.

Thanks.

As has been pointed out, the koffice apps are not available as binaries, so if you want to use them, you'll have to compile them yourself.

However, be careful. I had an, um, "interesting" experience with koffice last weekend. I have the latest kde installed from binaries on my 2002 Quicksilver G4 933. It works great, and I even got the font smoothing/anti-aliasing to work thanks to a tip from this forum.

I installed kword, kspread, and karbon:

$ fink install kword kspread karbon

The compile (about 20 hours worth) seems to have completed successfully. There were no error messages, but it caused some very strange/broken KDE behavior. I start KDE and the following happens:

1) The KDE splash screen comes up as usual

2) I get an error dialog:

Error while initializing the sound driver:
couldn't auto detect which audio I/O method to use
The sound server will continue, using the null output device.

and then there's no KDE startup sound.

3) The KDE panel never opens, so I have no GUI way to open any of the KDE apps or log out of KDE. kword will launch from the command line, though.

For now I just nuked /sw and restored it from the previous day's backups (and KDE behavior is back to normal), but if you're going to try to compile/install koffice on your machine, be sure that you have a recent backup of your /sw directory in case the compile/install breaks your KDE.

I think I'll try it one more time and see if I can post any error messages to the fink-beginners mailing list to try and resolve this.

Or I may just wait until koffice is available as binaries.

-g

[wataru]

Originally posted by gitbox:
2) I get an error dialog:

Error while initializing the sound driver:
couldn't auto detect which audio I/O method to use
The sound server will continue, using the null output device.

and then there's no KDE startup sound.

I get that with KDE default settings. Fix it by changing the sound output setting in the Control Panel from Autodetect to the something-or-other sound server. It's the only other option, excluding the null sound output.

Of course if you can't get into the Control Panel then I don't know how to do it.

[Turnpike]

Okay, so after all that it simply didn't compile for me. It gets a decent distance across the progress bar (a little less than 2/3, I'd say) and spits out the following error message while compiling "doxygen" :

ld: warning prebinding disabled because dependent library: /usr/local/lib/libpng.3.1.2.5.dylib is not prebound
ld: Undefined symbols:
_crc32
_inflateReset
_deflate
_deflateEnd
_deflateInit2_
_deflateReset
make[2]: *** [../bin/doxygen] Error 1
make[1]: *** [all] Error 2
make: *** [all] Error 2
### execution of make failed, exit code 2
Failed: compiling doxygen-1.3.7-1 failed

When I try again to compile it (this is all using FinkCommander, by the way) it starts up in the same place (compiling doxygen). It also gives me a choice of two possible packages that would fill a dependency. Although this isn't the package it is having trouble with, I've tried both anyway. Needless to say, no difference. For now I'm going to try and compile the other packages that are listed to be installed, in hopes that some workaround shows up or something. Any ideas?

Also, on a bit of a side note... what is the preferred method of backing this stuff up? Will a simple burning of the /sw directory to a CD be enough, or is something else required?

Thanks again

[wataru]

Originally posted by Turnpike:
Also, on a bit of a side note... what is the preferred method of backing this stuff up? Will a simple burning of the /sw directory to a CD be enough, or is something else required?

Thanks again

I'd like to know that, myself. My /sw is now almost 4GB; I'd like to be able to store some of that (probably just the .deb and source files) on an external drive.

The latest doxygen is also available by binary; why don't you just install that separately?

[Turnpike]

installing doxygen as a binary is a no-go... for one, it isn't the latest version. However, it seems to be new enough to count for koffice.

problems arose with one of the library files... don't have it on-hand, but I believe it was kdelibs3-ssl-shlibs or something like that. Similar thing, wouldn't compile. Not sure if it was for the same reason as doxygen or not, or if it was because of the older version of doxygen (it wasn't listed as a dependency). I already have the latest binary of said library. koffice seems to want the newer source version.


Unless anybody has some miracle fix, it looks like I'm sticking with OpenOffice.org for a while, until koffice gets some binaries out there. Thanks for the efforts, though.

[wataru]

What are you talking about? I have the latest doxygen listed as 1.3.7-1 in both binary and source, and I just updated from CVS about 2 seconds ago.

Wait, are you running OS X 10.2 or 10.3?