There have been several posts here about getting GnuCash to work in Slackware. My solution has usually been to install a complete Gnome environment (most recently GSlacky, because it already had GnuCash in it). Since I converted to 12.2, I haven't been using GnuCash, no GSlacky, yet. However, in the past few days, a build script for GnuCash was added to SlackBuilds.org. There are, of course, a number of gnomish dependencies that must be installed first, but I use sbopkg, so that process was relatively painless. I want to thank Vincent Batts, the GnuCash.SlackBuild author, Eric Hanson, the maintainer of most of the deps, Chess Griffin, the sbopkg author & everyone associated with SlackBuilds.org; you have made my Slackware experience much nicer.
Regards,
Bill

I can second that. I also use sbopkg as a management tool for slackbuilds.org and it allows you to build GnuCash and all the dependencies with one operation queue.

samac

IMHO, SlackBuilds.org has been one of the best developments in the Slackware community in some time. It is an absolutely fantastic resource, and I would also like to the thank the script maintainers and the SBo admins for making it so great.

I am also glad that sbopkg has been working well for both of you. There has been a lot of 'under the hood' improvements and bug fixes in SVN since the last release, especially to the update feature and the build queue. A new release should be out pretty soon so stay tuned! :-)

I use it and love it, awesome tool.

Yes, I wholeheartedly agree. Slackbuilds.org is a great resource of reliable build scripts. I also use sbopkg. It makes installing software a little more automated. I use it regularly and love it.

I agree. There is now a bunch of really excellent and comfortable package management utilities available.

sbopkg is great for SlackBuilds.org.
src2pkg makes installing from source a breeze, when there is no SlackBuild or binary package available for Slackware.
slackyd is also convenient for stuff hosted at slacky.eu.
And I even like some of the features of slaptget, e. g. the dependency check and the multi-repository list of available updates. I don't use it to install or upgrade software with it, because I don't want to be sent to dependency hell, but I keep track, how current my 3rd party software is with it. Which comes to a large part from slacky.eu and for a smaller part from LinuxPackages.net (no flamewar, please: there are quite a few *good* packages available there, e. g. everything from Ken Zalewski).
But for system patches I use slackpkg.

A nice little zoo of helpful tools and utilities. IMHO, src2pkg and sbopkg are so good that they should be considered candidates for inclusion in future releases of Slackware.

Thanks to the authors of all these helpful programs, and to the package maintainers of the three to five most relevant repositories for Slackware 3rd party stuff (SlackBuilds.org, slacky.eu, linuxpackages.net, and the stuff from Eric Hameleers and Robby Workman on their respective home pages) and all the smaller ones, too many to mention here!

gargamel

Src2pkg should definitely be included. I only use trackinstall from time to time, but gnashley is definitely doing some fantastic work here. I will look into sbopkg when I find some time, it sounds promising as well.

Thanks, I never heard of sbopkg

Without slackbuilds.org I wouldn't use Slackware.
Because even if I know how to compile software myself, it takes a long time to find how to compile when it's not ./configure && make && make install.

Same

That is true, but if you read the SlackBuilds you use, along with a copy of The Advanced BASH Scripting Guide, to help you with things you don't understand, you will catch on soon enough. I wrote several perfectly worthless build scripts before I started catching on & I still read every script I can find to get tips I can use. Mostly, though, I start with the SBo template & go from there.
Regards,
Bill

In my attempts to get GNUcash up and running, I get this error message at build time.

> No package 'libbonobo-2.0' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables LIBGNOME_CFLAGS
> and LIBGNOME_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.

I understand that I have about twenty packages to build an install.I read the package_config man page.
New to SlackWare how an where do set the above variables?

P.S. I have installed some packages via sbopkg.

Thanks in Advance!

The error message is caused by the build script looking for an installed libbonobo-2.0 package. Certain files in that package are required to properly build gnucash.

The libbonobo is required to be built and installed before trying to build the gnucash package. According to the slackbuild gnucash web page:

This requires the following additional software, and it is suggested
that you build them in this order:

slib
libofx
ORbit2
GConf
libtasn1
gnome-keyring
gnome-mime-data
libbonobo
gnome-vfs
gail
libgnomecanvas
libgnome
libbonoboui
libgnomeui
libgnomecups
libgnomeprint
libgnomeprintui
gtkhtml
goffice

So download, build, and install each package in the listed order. Then build gnucash.

I hope this helps.

Thanks Woodsman.
That is exactly what I'm doing. Unfortunately, when I reach the package "libgnome" it won't compile.
I get an error message at build time. The error message states that I haven't installed a package that "libgnome" depends upon. Since I do have the package in question installed. I believe that some package version may be wrong, or "libgnome" can't see it at build time.
The error message implies that I can adjust something called "make_config" to get around the error. However, I read the man page for "make_config", and I can't make heads or tails of it.
It probably wouldn't hurt for me to e-mail the guy that created the Slackbuid.
I can't get a major package required by gnucash to build and install.

P.S. Running out of time.I may have just use MoneyDance.MoneyDance is a great program, but I,m not to crazy about using a Java application to manage my finances.

Its a good idea after each new software install to run ldconfig as root.
Makes it easier for the next build to find stuff.