[GRASS-dev] Wrong sqlite3.dll used on MS Windows

[Vaclav Petras]

Hi,

here is some minor issue on MS Windows, did somebody experienced something
like the following?

GRASS was not starting for one student on MS Windows. The reported error
was that it cannot find some symbol/procedure in sqlite3.dll. The problem
was possible to workaround by finding another sqlite3.dll on disk and
renaming it to something arbitrary.

The strange think is that GRASS directory extrabin should be, and indeed
is, at the beginning of PATH variable, so it should look first there.
However, because of the error and fix it seems that it is looking elsewhere
first.

What was also strange is that the other DLL was in SysWoW64 directory and I
don't see this directory on PATH (in or outside GRASS session) but if I
understand correctly, there is some magic which makes system32 directory
(which contains 64bit libs on 64bit system) to link to SysWoW64 (where are
32bit DLLs) for 32bit applications. Wow!

Still, there is no reason why it should pick the system directory, unless
it is using some other magic.

Any ideas?

Vaclav



Related:

The procedure entry point sqlite3_rtree_geometry_callback couldn't be
located
http://trac.osgeo.org/grass/ticket/2197#comment:1

WoW64
http://en.wikipedia.org/wiki/WoW64

How to fix "The entry point for the procedure sqlite3_open_v2 cannot be
found in the dynamic link library sqlite3.dll"
http://gis.stackexchange.com/questions/30432/how-to-fix-the-entry-point-for-the-procedure-sqlite3-open-v2-cannot-be-found-in
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20141006/28020ad9/attachment.html>