According to configure.in, zebra-0.5 requires python>=2.3.5. However, it uses "python-config", a utility that only appears to have be available in python starting in 2.5. Further, the detection for "python-config" (that name, first occurrence in PATH) isn't really correct logically. AM_PATH_PYTHON looks for all sorts of things besides just "python" (it finds "python2.5" on my machine), so it would be safer/saner to fall back to (or maybe use first?) "$PYTHON-config" instead of AC_CHECK_PROGS(python-config).
OTOH, even python-config is being mis-used...falsely assumes that --libs gives sufficient flags to link against libpython if that lib isn't in the standard compiler search path. Need to use --ldflags instead to get the -L also.
Overall, I'd say python-config should be scrapped and instead use $PYTHON directly to get the flags.
Logged In: YES
user_id=1377683
Originator: NO
thanks for this feedback!
i attempted to address all of this:
* configure should now use $PYTHON-config as indicated
* falls back to $PYTHON with a similar incantation for versions < 2.5
* the proper compile/include flags should now be selected
* the link with libpython was removed along w/associated flags - none of this should be necessary for a module
the fix is available in svn (rev 72), i also released a snapshot in case that is easier to test with...
-spadix
fixes available in release 0.6
This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).