Re: PGFoundry binaries

Bingo, adding -lsecur32 to the libs directive in Makefile.PL fixes the problem.



Anyways, managed to get 2.8.7 compiled and up. Also, got the easy urls working, too.



So, to install, choose one of:



ppm install http://dbdpgppm.projects.postgresql.org/DBD-Pg-5.10.ppd

ppm install http://dbdpgppm.projects.postgresql.org/DBD-Pg-5.10s.ppd



ppm install http://dbdpgppm.projects.postgresql.org/DBD-Pg-5.8.ppd

ppm install http://dbdpgppm.projects.postgresql.org/DBD-Pg-5.8s.ppd



ppm install http://dbdpgppm.projects.postgresql.org/DBD-Pg-5.6.ppd

ppm install http://dbdpgppm.projects.postgresql.org/DBD-Pg-5.6s.ppd



Also, the following files may be needed:

http://dbdpgppm.projects.postgresql.org/msvcr80.zip

http://dbdpgppm.projects.postgresql.org/openssl.zip




T.J.



Greg Sabino Mullane wrote:

  -----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160



  Not sure where it came from or why I started getting it. I thought maybe

  ...

  Should I send a message off to pgsql-bugs? If I can fix this
long standing problem I've had I'm sure I can keep up with your
two week release cycle Greg  ;)

  
Well you got further than I did. :) I actually tried a fresh Windows
install of Perl and Postgres, but could not compile as the Postgres
INCLUDE directory seemed to be missing.


  libpq.lib(fe-connect.obj) : error LNK2019: unresolved external symbol
__imp__FreeCredentialsHandle@4 referenced in function _closePGconn

  
Google seems to suggest this is due to a missing secur32.dll or
not including Security.h. But I'm not a Windows programmer, so
email to -hackers (probably not -bugs) is probably a good idea.

- --
Greg Sabino Mullane greg-738XdyZ4GzZWk0Htik3J/[email protected]
PGP Key: 0x14964AC8 200807250924
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iEYEAREDAAYFAkiJ1CwACgkQvJuQZxSWSsgvYQCfZPoSAWZ7Jp2Hq+aSF3KX+jxB
/aEAn1XFhfZYnBxkFKag0McEUaSfwS7t
=WlTc
-----END PGP SIGNATURE-----