The Mac bundle has its own copy of sqlite3 along with almost everything else it needs. It does use some frameworks from /System/Library/Frameworks (notably AppKit and CoreFoundation) and one or two from /usr/lib. It does not and cannot use anything from Homebrew; the Homebrew “recipe” for GnuCash just retrieves and downloads one of our distribution dmgs.
Regards, John Ralls > On Apr 9, 2018, at 2:13 AM, coolnodje <coolno...@gmail.com> wrote: > > sqlite is still installed and available on my machine. > I can't make sure which version is used though, as there are several > and I don't quite get which PATH Gnucash is using on MacOS. > > It's very likely that it uses the MacOS pre-installed version and that > it hasn't changed. > > If Gnucash has access to the specific "brew" installed binaries then it > may be that a newer version isn't compatible. > > -nodje > > On 08/04/2018 14:33, David Carlson wrote: > > Did you verify that you had the back end installed? see > [1]https://wiki.gnucash.org/wiki/FAQ#SQL_Database > David C > > On Sun, Apr 8, 2018 at 7:10 AM, coolnodje <[2]coolno...@gmail.com> > wrote: > > Using Gnucash on MacOS, I got this error trying to open a recently > created file which I think I based on a database back-end instead of > the > standard. > I have upgraded to 3.0 in the meantime and thought it was the > problem. > But I realized when I finally was able to start a v2.6.20 on an > older > MacOS10.12 virtual machine that I still had the problem. > Which means that this is all unrelated to the 3.0 upgrade. > I've tried to revert the file to an older version (prior to the last > modification, so prior to the last successful opening) but got the > same > error. > This really confuses me: > - the file as it was the last time it was successfully modified > cannot > be opened (which should exclude file corruption problem) > - the latest version on latest MacOS can't open it because "No > suitable > backend", but 2.6.20 on MacOS10.12 also can't open it because "No > suitable backend". > So if the file itself is not the problem, and if version that used > to be > able to open it can't anymore, where could the problem come from? > Only I wasn't able to reproduce the error with the exact same setup > I > had when last successfully modified: trying to reinstall 2.6.20 on > MacOS10.13 I realized it can't be started anymore (Gnucash can't be > opened because of a problem - DYLD, [0x4] Symbol missing) > Is there anything I can do to try to save the file in question? > - nodje > _______________________________________________ > gnucash-user mailing list > [3]gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > [4]https://lists.gnucash.org/mailman/listinfo/gnucash-user > If you are using Nabble or Gmane, please see > [5]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. > > References > > 1. https://wiki.gnucash.org/wiki/FAQ#SQL_Database > 2. mailto:coolno...@gmail.com > 3. mailto:gnucash-user@gnucash.org > 4. https://lists.gnucash.org/mailman/listinfo/gnucash-user > 5. https://wiki.gnucash.org/wiki/Mailing_Lists > _______________________________________________ > 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.
