[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Compiling gnucash 1.7.7 for Woody?



Michael D. Crawford wrote:
I would like to try out the new GnuCash 1.7.7. It has some small business features I'd find helpful, and is supposed to have an easier way to handle foreign currency exchange, among many other new features.

I want to install it on a PowerPC woody system, a Mac 8500.

GnuCash 1.7.7 is available in unstable. I know how I can use apt pinning to install an unstable package in a stable system. However, I'm concerned because GnuCash has many dependencies. Trying to install the unstable 1.7.7 in my woody system might clobber it because so many dependencies from unstable will get installed.

So what I think I would like to do is download the 1.7.7 debian sources, and compile it on my woody system. I would need to make sure I had all the dependencies, but I would be getting stable dependencies.

I've managed to compile debian packages before but I've only done it a couple times.

GnuCash is supposed to be rather daunting to compile yourself, because it has so many dependencies.

Would this have the desired effect? Can anyone tell me if GnuCash 1.7.7 requires dependencies, or versions of them, that aren't available at all in Woody?


It requires two build dependencies not available in Sarge[there may be additional dependencies that Woody doesn't have]: libofx-dev and a newer version of libgwrapguile-dev. Presumably you can backport these in the same manner as you are going to backport gnucash. Since presumably you are going to be compiling with 2.95, you should probably remove the c102 from the package name of libofx0c102 to avoid possible pain down the road and fix the attendant problems that arise, but since libofx0 never existed this is also likely to cause problems down the road, so you just have to remember to deal with these problems at the appropriate time whichever route you choose. The best choice might be to leave it as libofx0c102, but decrement the version number to ensure that it is upgraded to the gcc 3.2 version at the appropriate time.

As for using apt-get build-dep: this is not much of a suggestion since apt-get is not what you would call verbose if it fails on an apt-get build-dep. A better tool is: "cat /var/lib/apt/lists/*Sources | grep-dctrl -FBinary,Package gnucash -s Package,Build-Depends" and then manually checking the build dependencies[of course if apt-get build-dep works than you are clear sailing...]



Reply to: