[MacPorts] #32500: libplist does not configure when Python 3.x has been selected

MacPorts noreply at macports.org
Sat Dec 10 22:04:16 PST 2011


#32500: libplist does not configure when Python 3.x has been selected
-----------------------------------+----------------------------------------
 Reporter:  gcrosswhite@…          |       Owner:  macports-tickets@…                   
     Type:  defect                 |      Status:  new                                  
 Priority:  Normal                 |   Milestone:                                       
Component:  ports                  |     Version:  2.0.3                                
 Keywords:                         |        Port:                                       
-----------------------------------+----------------------------------------
 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/32500>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list