Please remember to copy the list on all replies. You're not entirely out of line with your criticism, the behavior is a bit unusual.
The build you reported is based on a git pull from February, so it's another build you did yourself, not something you pulled in with apt. If you're sure that there's no instance of gnucash's modules anywhere on the link path (that includes CMAKE_INSTALL_PATH as well as the standard directories of /usr/lib and /usr/local/lib) then check the source path you gave to cmake. You might not be building the sources you think you are. Regards, John Ralls > On Apr 2, 2019, at 2:48 AM, Mark Sattolo <[email protected]> wrote: > > Still plugging away at it. Clearly there are some build settings on my > platform that are a problem... Sorry if I sounded critical before. I was just > surprised. I haven't had to work with C/C++ builds for a while... I > appreciate all the work you guys put into keeping Gnucash a viable > alternative. > > > Tks, > > On Mon, Apr 1, 2019, 19:19 Mark Sattolo <[email protected]> wrote: > According to dpkg, all my gnucash packages are in > /usr/lib/x86_64-linux-gnu/gnucash/ so I removed that and built again from > scratch. No difference. I'm not going to worry about it anymore. Thanks for > your time. > > cheers, > > Mark Sattolo > [email protected] > > (613) 447-5385 > > > > On Mon, Apr 1, 2019 at 6:44 PM Mark Sattolo <[email protected]> wrote: > Sorry, just twigged on, I think... You mean you have to remove your existing > system gnucash, if any, in /usr/lib/x86_64-linux-gnu/gnucash/ etc. before you > can build a proper version 3.5? That doesn't sound very friendly... Should > the build really be set up that way? Is that the only way you can do a proper > build? > > thanks again, > > Mark Sattolo > [email protected] > > (613) 447-5385 > > > > On Mon, Apr 1, 2019 at 6:38 PM Mark Sattolo <[email protected]> wrote: > Not sure what you mean by 'clean out your installation'? All my packages are > fully up-to-date according to 'apt update' and 'apt-get build-dep gnucash'. > The build instructions don't mention anything about 'cleaning out your > installation'... I am building from code freshly extracted from the 3.5 > tarball in a clean build folder. What is it in my /usr/lib folders that can > be knocking my build down from 3.5 to 3.4-80? Sorry to trouble you with this. > > cheers, > Mark Sattolo > [email protected] > > (613) 447-5385 > > > > On Mon, Apr 1, 2019 at 6:12 PM John Ralls <[email protected]> wrote: > > > > On Apr 1, 2019, at 2:53 PM, Mark Sattolo <[email protected]> wrote: > > > > I built the source code from tag 3.5 but I get this from the resulting > > executable: > > 2013 > gnucash --version > > GnuCash 3.4 development version > > Build ID: git 3.4-80-g6e4761911+ (2019-02-04) > > > > I get the exact same report from the executable built from the > > gnucash-3.5.tar.gz mentioned above... > > > > Shouldn't it say 'GnuCash 3.5 stable version' ? > > They should, and both the Mac and MSWin builds--built from that same > tarball--say: > GnuCash 3.5 > Build ID: 3.5+(2019-03-30) > > Note the date on that commit, 4 February. That was a lot of commits ago. > > Did you clean out your installation before building? GnuCash uses dlopen to > open its module libraries during the build and ld will look first in the > standard installation directories like /usr/lib before looking in the build > directory. That can cause all manner of trouble. > > Regards, > John Ralls > _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
