Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue in windows 7 64bit #812

Closed
ElyDotDev opened this issue Jan 12, 2018 · 1 comment
Closed

Issue in windows 7 64bit #812

ElyDotDev opened this issue Jan 12, 2018 · 1 comment

Comments

@ElyDotDev
Copy link
Contributor

I've tried to use the latest version binary built artifacts from appveyor (also mentioned 0.94.0 link in Readme), and run on windows 7 64bit. But I've got an error about CreateFile2 not located in KERNEL32.dll. But latest 0.92.0 binary works like a charm on my OS. So I done some searches to find out what's the cause of the problem. Here are whats I found:

  1. Latest working binary: 0.0.352
  2. First successful built binary that doesn't works: 0.0.397
  3. The built binary that doesn't works with existing commit (previous commit was deleted so cannot compare those commits): 0.0.402
  4. Compare of those two commits: Compare 18880484c5f4e9e7f11a51b4c2a36f601af05e5a and 6c6dcd152c6c1fddfc197b94de137a44ffcf7c1f

Well found nothing by comparing those two (not familiar with the osm2pgsql project very well), So do some more searches and found that there is a regression in zlib that osm2pgsql uses, with the same behavior. The regression is in zlib 1.2.8 and fixed in 1.2.9. By reading the log files of appveyor builds, found Found ZLIB: C:/libs/lib/zlib.lib (found version "1.2.8") line, so osm2pgsql uses the same version with regression. So I think the problem came from zlib. I really needs osm2pgsql latest version that works on my OS, and above results are the all things I can do to find a fix for the problem.

@ElyDotDev ElyDotDev changed the title zlib issue in windows 7 Issue in windows 7 64bit Jan 12, 2018
@ElyDotDev
Copy link
Contributor Author

It's been fixed by merged PR #820. Also by the PR, issue #803 fixed two. I'm closing this issue and it's OK to close #803 issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant