libplist does not configure when Python 3.x has been selected

[gcrosswhite@…]

The configuration script for libplist uses code that is not Python 3.x compatible. Specifically, in the file swig/CMakeLists.txt:11-14 (in version 1.4 of libplist) we have:

EXEC_PROGRAM("${PYTHON_EXECUTABLE}"
    ARGS "-c 'try:\n import distutils.sysconfig; print distutils.sysconfig.get_python_lib(plat_specific=1)\nexcept: pass\n'"
    OUTPUT_VARIABLE DISTUTILS_PYTHON_ILIBRARY_PATH
    )

Unfortunately, if the MacPorts selected Python varient is 3.x (i.e., someone ran something like "select --set python python3.1), then the code above produces an error because it uses the selected Python 3.x executable which barfs on the configuration code, causing the port to fail to configure. I was able to work around the problem by temporarily running "select --set python python27", whence libplist was able to build.

[gcrosswhite@…]

Cc Me!

[ryandesign (Ryan Carsten Schmidt)]

This is basically a further consequence of #27094 and would presumably be resolved by resolving that ticket.