-
Notifications
You must be signed in to change notification settings - Fork 88
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
installation fails on windows 10 #60
Comments
@Huisong-Li Thanks for trying out pg_query! It seems your client fails to verify the certificate when downloading I'm unfortunately not familiar with Ruby on Windows, so can't really advise as to why this is failing. |
@lfittl Thank you all the same! |
@Huisong-Li Unfortunately the way the gem works, you can't really setup the C library independently right now. If you can't get the CA certificate issue to work, it might be easiest to fork the gem and adjust the extconf.rb file to accept invalid certificates. I might also resolve this in a future release by taking an approach similar to the Go library, which already includes a copy of the C library. |
Same issue. |
I believe the issue is in extconf.rb
Using windows, IOW, I tried
and it didn't work.
worked fine. Hope this helps... |
Thank you @MSP-Greg , I did change the extconf.rb file and it does pass to generate makefile. I try make install for this gem. it got new errorD:\ruby\ruby_packages_nobk\rubyinstaller-2.5.0-snapshot-x64_aug29\lib\ruby\gems\2.5.0\gems\pg_query- Seems it require some lpg_query, I am trying figuring out. |
@Huisong-Li I too got the same issue as you but on Ubuntu. Figured out, it was due to my network being behind a proxy. I set the cc @lfittl |
Thought I'd take a look at at this re Windows. Made some changes here and there. I'm now stopped at
Can't seem to find
Just forked |
@MSP-Greg Hmm, I suspect we'd need to teach the extraction logic in libpg_query about considering Windows, and keeping the Windows code parts of Postgres intact. Since I don't have access to a Windows system this makes it a bit difficult for me to help on this, but if someone wanted to work on this, I would recommend looking into setting up LLVM + Ruby bindings, and then modifying the extract_source.rb script in libpg_query to do the right thing. We might also need to have some more of these defines set on Windows, since we don't have All in all this is not an easy task, as you say. |
I did look at the extraction logic. Haven't stated it anywhere here, I'm a ruby coder & I build a lot of ruby code (and 'extension' gems) on windows. But, critical issue, I don't know c. I can read it and get a general idea, but that's about it. IOW, even if I had the time... Thanks. |
Any updates on this? Got the same issue :/ |
@paulolopesrb No updates yet - Windows support is a known limitation right now. I've tried to get this into the new 2.0 release, but ultimately ended up not making it because of time constraints. This is still on my list though, and I hope to get to it in the next months. Contributions are welcome, but they'd need to be made in libpg_query directly - if you can figure out the necessary header changes (like discussed a bit above), that would make my life a lot easier, and enable me to fix this faster. |
Hello, this is a very old issue. I also tried installing it using Ruby+Devkit 3.2.2-1 (x64) on windows 10 and got the following stacktrace:
It seems to be missing a file ? |
Windows support has been added in #305 and released as part of 5.1.0. |
when i first time tried to install pg_query i failed
it reminded me to install DevKit
i installed it then test installtion as follow
https://github.com/oneclick/rubyinstaller/wiki/Development-Kit#5-test-installation
DevKit works well
and i tried again to install pg_query, it reminded me as follow:
i work on windows 10 amd 64
ruby 2.3.3p222 (2016-11-21 revision 56859) [i386-mingw32]
i installed all dependce from
https://rubygems.org/gems/pg_query/versions/0.9.2
no matter runtime or devlopment
and i also installed postgresql 9.6 (X86)
The text was updated successfully, but these errors were encountered: