[MacPorts] #15426: BUG: py25-* fail with parallel building enabled

[MacPorts]

#15426: BUG: py25-* fail with parallel building enabled
---------------------------------+------------------------------------------
 Reporter:  raimue at macports.org  |       Owner:  afb at macports.org  
     Type:  defect               |      Status:  new               
 Priority:  Normal               |   Milestone:  MacPorts base bugs
Component:  base                 |     Version:  1.7.0             
 Keywords:  parallel             |  
---------------------------------+------------------------------------------
 There was a new bug introduced while fixing #15295.

 {{{
 --->  Building py25-bz2 with target build
 DEBUG: Executing org.macports.build (py25-bz2)
 DEBUG: port allows a parallel build
 DEBUG: Environment: "MACOSX_DEPLOYMENT_TARGET"='10.5'
 DEBUG: Assembled command: 'cd
 "/opt/local/var/macports/build/_Users_raim_src_macports_trunk_dports_python_py25-bz2/work/Python-2.5.2/Modules"
 && /opt/local/bin/python2.5 setup.py build'
 usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
    or: setup.py --help [cmd1 cmd2 ...]
    or: setup.py --help-commands
    or: setup.py cmd --help

 error: option -j not recognized
 Error: Target org.macports.build returned: shell command " cd
 "/opt/local/var/macports/build/_Users_raim_src_macports_trunk_dports_python_py25-bz2/work/Python-2.5.2/Modules"
 && /opt/local/bin/python2.5 setup.py build  -j3" returned error 1
 }}}

 The python port groups just set build.cmd (and do not overwrite
 build.type), so [build_getmaketype] still assumes this is a standard make.
 With the previous implementation overwriting build.cmd was enough.

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