What was likely the problem is missing or screwed up dependencies. For any SlackBuild on slackbuilds.org (SBo), they are required to have all dependencies available. If you browse the site, it will list any required packages at the bottom of the README section. For xournal, you only need libgnomecanvas since libgnomecanvas has no dependencies itself.
In regards to slapt-get, if things were placed in /usr/lib/ instead of /usr/lib64/, you might have slapt-get configured to a 32bit mirror/repo instead of a 64bit one. That could lead to xournal not recognizing the dependency since it's for the wrong system. sbotools went through and built libgnomecanvas and installed it, then it built xournal and installed that. It should work its way through dependencies for you. Be careful about installing packages from multiple repositories as they aren't guaranteed to work with each other (they could've been compiled differently or relying on different dependencies that might even been different versions).
So far, I only have experience with sbopkg (requires a bit of extra work for dependencies using the included sqg) and slackrepo. The creator of slackrepo (David Spencer, aka 55020) is very active on this forum and is one of the admins at SBo. He recently created
dusk, which automates building newer kernels when they're released by kernel.org and providing Slackware packages to us (if you want to trust him, but he also provides scripts so you can do it yourself). slackrepo is fully functional. I know he still has plans on his todo list, but it
However, with slackrepo, keep in mind that it is designed to be run on a clean install. When it builds a program, it will create an overlayfs and then chroot to it so it doesn't modify your system at all. Once the program is compiled, the chroot is destroyed and your system remains clean. Because of this, you shouldn't use slackrepo on your primary machine as you'll obviously want to install the programs you compile. You'd either need a dedicated machine or a VM (I use a VM because I don't have an extra machine that can stay clean). Because of the design, slackrepo is not for everyone. It is better suited to people who have Slackware on at least 2 or more computers, because then you can have your slackrepo machine create, well, a repo that both machines can connect to and download and install packages.
For managing a single computer, it would probably better to stick to one of the other tools... sbopkg, sbotools, slpkg, etc. Feel free to install all of them and try them out to see which one you like the best.