Thanks Dave, I forgot about the README.dependencies file. I’ll take a look.
I knew I was going to get some useful feedback from gcc and ./configure, I just didn’t know how messy it was going to be. I appreciate the tips on prefix and paths. That explains why I had trouble with a recent build of 2.7 turning into a mess with an older 2.6 from the official repo still installed. Sometimes you find instructions that assume you know all the implications of a choice, I guess I didn’t. Glad to know you successfully built 2.6.19 on 4.13.0-36 as that’s the same one I’m working with. I’ll give it a go this afternoon. Regards, Adrien > On Feb 27, 2018, at 12:05 AM, DaveC49 <davidcous...@bigpond.com> wrote: > > Just an additional comment Adrien, > > ./configure usually checks all the dependencies. First time I compiled > gnucash from sources I just reran ./configure installing any packages it > flagged as missing. i've just recompiled 2.6.19 on Linux Mint 18.3 (Ubuntu > 16.04 derivative updated to Linux kernel version 4.13.0-36) without any > hassles and it's working fine. > > David > > > > ----- > David Cousens > -- > Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-User-f1415819.html > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists for more information. > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.