Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Can only specify static-libpq in setup.cfg

#47

This is extant in the current 2.4 release.

The current setup.py only allows setting the static-libpq option
via the setup.cfg, and doesn't accept it on the setup.py commandline.
Instead, you get the following error:
error: error in command line: command 'psycopg_build_ext' has no such option 'static_libpq'

I've attached a minimal patch which makes it work, tested on RHEL-5 and OSX.

Reported by Matthew Ryan · March 9th, 2011 @ 04:57 PM

State: resolved
Milestone: none
Assigned to: nobody

Activity

  1. Daniele Varrazzo
    Daniele Varrazzo
    • Tag set to patch, setup
    • State changed from new to open

    Thanks, I think there is no problem in merging the patch.

    March 16th, 2011 @ 12:07 PM

  2. Daniele Varrazzo
    Daniele Varrazzo
    • State changed from open to resolved

    I'm merging the patch. However for me (on ubuntu) the compiled library doesn't work:

    Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/piro/dev/psycopg2/build/lib.2.6/psycopg2/__init__.py", line 71, in <module>
    from psycopg2._psycopg import BINARY, NUMBER, STRING, DATETIME, ROWID
ImportError: /home/piro/dev/psycopg2/build/lib.2.6/psycopg2/_psycopg.so: undefined symbol: GSS_C_NT_HOSTBASED_SERVICE
make: *** [check] Error 1

    I suspect what is missing is linking against the crypto libraries. The problem is not in the patch anyway: you get the same setting static_libpq in setup.cfg. So I'll leave people who know what to do (which is not me) solving the problem specifying --libraries too.

    March 26th, 2011 @ 01:42 PM