build error CentOS 7 PG_INT64_TYPE #520
Closed
Comments
I would have said PG 9.1 should have worked as well. It doesn't seem the case. Taking a look... |
|
dvarrazzo
added a commit
that referenced
this issue
Mar 2, 2017
Building with 9.2 reported failing on CentOS 7 in issue #520. This commit is expected to fail build in Travis CI.
dvarrazzo
added a commit
that referenced
this issue
Mar 2, 2017
Only defined in Postgres 9.3 Should close #520, but let's wait for the CI response (build on Windows etc.)
Hey @dvarrazzo, Thanks for the timely update. Adding your libpq_support.h patch, I was able able to build RPMs. Do you think a 2.7.1 release will be coming soon, or should I proceed with building 2.7 with the patch? |
There are a few bugs already open and fixed with 2.7: a 2.7.1 may come out in a few days/one week. |
Thanks for the additional information. I think we will just wait for 2.7.1. |
I got email notification about being mentioned on #518 and will reply. |
dvarrazzo
added a commit
that referenced
this issue
Mar 2, 2017
Building with 9.2 reported failing on CentOS 7 in issue #520. I would leave this commit in a branch aside for the moment, because this is useful but it cannot replace building with more modern libpq, because some features are not compiled in and some tests skipped.
@dvarrazzo I'm late to the party, but the fix looks fine. There are uses of |
dvarrazzo
added a commit
that referenced
this issue
Mar 11, 2017
Building with 9.2 reported failing on CentOS 7 in issue #520. I would leave this commit in a branch aside for the moment, because this is useful but it cannot replace building with more modern libpq, because some features are not compiled in and some tests skipped.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am attempting to build psycopg2 2.7 for Python 3.6 on CentOS 7 and are getting the following error:
Note, CentOS 7 uses Postgresql 9.2.18. From what I can tell, PG_INT64_TYPE was introduced in Postgresql 9.3. Is Postgresql 9.2.X supported? Any recommendations on a patch file to work around this?
The text was updated successfully, but these errors were encountered: