Dear Phil, I've tracked down the bug below, which said some of the full win32 gnucash binary has a dependency on MSVCR71.DLL. That's the C runtime library of the rather old Microsoft Visual Studio compiler version 7.1 (Visual Studio 2003, I believe). Your pgsql binary package introduces this dependency into the gnucash win32 package.
This kind of compiler-specific DLL cannot be expected to be present on the target system, so if it is really needed, one would have to include it in our binary package. However, in this case it rather means the binary DLLs for PgSQL which you collected from somewhere else have been compiled by that old visual studio compiler. Is this really necessary? Isn't there some way to get this without a dependency on the visual studio runtime? Oh, and there's a much more severe error, as mentioned by me in the bugzilla item: By including the suitable openssl DLLs (libeay32.dll, libssl32.dll, ssleay32.dll) in your pgsql binary, you're silently overwriting those openssl DLLs which we compile ourselves during the win32 build, and on which the aqbanking library depends upon. In other words, the inclusion of the current pgsql binary package most probably will cause any SSL-related operation of aqbanking to crash badly. I propose to remove the pgsql part of the win32 binary for now, until we (resp. you) have found a better pgsql binary to include in our build. Regards, Christian ---------- Weitergeleitete Nachricht ---------- Subject: [Bug 596248] MSVCR71.dll not found error on startup Date: Samstag, 3. Oktober 2009 15:48 From: "GnuCash" (bugzilla.gnome.org) <bugzi...@gnome.org> To: stimm...@tuhh.de https://bugzilla.gnome.org/show_bug.cgi?id=596248 GnuCash | Windows | 2.3.5 --- Comment #6 from Christian Stimming <stimm...@tuhh.de> 2009-10-03 13:48:36 UTC --- The following DLLs in our installation's "bin/" folder in r18363 exhibit a (direct or indirect) dependency on MSVCR71.DLL: ssleay32.dll libeay32.dll krb5_32.dll k5sprt32.dll gssapi32.dll comerr32.dll These DLLs are all installed from the "pgsql" package, which in turn is being downloaded as a tarball from the gnucash.org site. In other words, our postgresql binary package is flawed and must not be used in this way. We need to fix this on our side. On a side note, the three openssl DLLs in the pgsql-win32.tar.gz tarball (libeay32.dll, libssl32.dll, ssleay32.dll) silently overwrite those which we compile from source and which are needed for aqbanking's SSL connections. We must not overwrite openssl DLLs with others. This needs to be fixed as well. -- Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. ------------------------------------------------------- _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
