Windows installer and dlls

Knut P. Lehre wrote:

Installing postgresql 8.2.0 on Windows XP Pro SP2 using the msi
installer dated 2006-12-04, with libeay32.dll and ssleay32.dll (both
dated 2005-07-06) (and libiconv-2.dll, libintl-2.dll, and libpq.dll)
from a previous installation (of version 8.0.5) already present in
c:\windows\system32. These files in system32 did not appear to be
updated during the 8.2.0 installation. Instead new files were placed
in the postgresql bin directory: new versions of libeay32, ssleay32,
and libpq, the same version as the present of libiconv-2
(2003-01-31), and, surprisingly, a libintl-2 with an older date
(2003-02-01) than the file already present in system32 (2004-04-27).
Is the libintl-2 supposed to be downgraded to a previous version?

Not really :) Dave, can you comment on this?

(it is correct that we don't *update* them, because we no longer touch
these files in SYSTEM32)

I uninstalled postgresql, removed the 5 files mentioned above from
system32. When I installed 8.2.0 again, the installer reported that
"The installer has detected an incompatible version of OpenSSL
installed in your system PATH. PostgreSQL requires OpenSSL 0.9.7 or
later. If you remove your OpenSSL files (LIBEAY32.DLL and
SSLEAY32.DLL) the installer will install the new version
automatically.". However, during the second installation, none of the
5 files mentioned above were reinstalled in system32, only in the
postgresql bin directory, as during the first installation. Is the
report of the missing libeay32 and ssleay32 a superfluous leftover
from the previous versions when these files were installed in
system32?

Are you sure they are not present in some *other* directory on your
system that's in the PATH?

//Magnus

Magnus Hagander wrote:

Knut P. Lehre wrote:

Installing postgresql 8.2.0 on Windows XP Pro SP2 using the msi
installer dated 2006-12-04, with libeay32.dll and ssleay32.dll (both
dated 2005-07-06) (and libiconv-2.dll, libintl-2.dll, and libpq.dll)
from a previous installation (of version 8.0.5) already present in
c:\windows\system32. These files in system32 did not appear to be
updated during the 8.2.0 installation. Instead new files were placed
in the postgresql bin directory: new versions of libeay32, ssleay32,
and libpq, the same version as the present of libiconv-2
(2003-01-31), and, surprisingly, a libintl-2 with an older date
(2003-02-01) than the file already present in system32 (2004-04-27).
Is the libintl-2 supposed to be downgraded to a previous version?

Not really :) Dave, can you comment on this?

There does seem to be some mismatches in the build repos for each
version. I'm not in the best place to sort that right now - any chance
you can sort it out? I uploaded an update to pgFoundry a few days ago.

Regards Dave

I uninstalled postgresql, removed the 5 files mentioned above from
system32. When I installed 8.2.0 again, the installer reported that
"The installer has detected an incompatible version of OpenSSL
installed in your system PATH. PostgreSQL requires OpenSSL 0.9.7 or
later. If you remove your OpenSSL files (LIBEAY32.DLL and
SSLEAY32.DLL) the installer will install the new version
automatically.". However, during the second installation, none of the
5 files mentioned above were reinstalled in system32, only in the
postgresql bin directory, as during the first installation. Is the
report of the missing libeay32 and ssleay32 a superfluous leftover
from the previous versions when these files were installed in
system32?

Are you sure they are not present in some *other* directory on your
system that's in the PATH?

//Magnus

You're right. After they were removed from both C:\windows and C:\windows\system32 the installer did no longer report incompatible OpenSSL version.

By the way: E.1.3.15. Win32 Port "Allow MSVC to compile the PostgreSQL server (Magnus, Hiroshi Saito)". Does this mean that the precompiled windows version of postgresql will be compiled by MSVC (I assume you can use the free 2005 express edition), or still by MinGW. I guess this will affect which compiler one should use for compilation of C-functions?

Thanks,
KP

Knut P. Lehre wrote:

I uninstalled postgresql, removed the 5 files mentioned above from
system32. When I installed 8.2.0 again, the installer reported that
"The installer has detected an incompatible version of OpenSSL
installed in your system PATH. PostgreSQL requires OpenSSL 0.9.7 or
later. If you remove your OpenSSL files (LIBEAY32.DLL and
SSLEAY32.DLL) the installer will install the new version
automatically.". However, during the second installation, none of the
5 files mentioned above were reinstalled in system32, only in the
postgresql bin directory, as during the first installation. Is the
report of the missing libeay32 and ssleay32 a superfluous leftover
from the previous versions when these files were installed in
system32?

Are you sure they are not present in some *other* directory on your
system that's in the PATH?

//Magnus

You're right. After they were removed from both C:\windows and C:\windows\system32 the installer did no longer report incompatible OpenSSL version.

By the way: E.1.3.15. Win32 Port "Allow MSVC to compile the PostgreSQL server (Magnus, Hiroshi Saito)". Does this mean that the precompiled windows version of postgresql will be compiled by MSVC (I assume you can use the free 2005 express edition), or still by MinGW. I guess this will affect which compiler one should use for compilation of C-functions?

This is not decided yet. It is my hope that it will be, but since it's
not on the buildfarm yet, we don't know.
What we do know is that all "point-releases" in 8.0/8.1/8.2 will be
built with MingW, we will absolutely not switch compiler until a new
major version.

//Magnus