Seems that the configure script of mpich2 doesn't check for anything higher than python-2.5, and when that is not found defaults python-2: (part of ./configure output) [snip] checking for python2.5... no checking for python2.4... no checking for python2.3... no checking for python2.2... no checking for python2... python2 checking for python... python checking that python2 is a valid python version... yes checking that the cPickle module is available for python2... yes [snip] this causes python files to be installed into /usr/lib/python2 folder and also the first line in python scripts becomes #!/usr/bin/env python2.5 thus making it impossible to run them directly if python-2.5 is not installed. Reproducible: Always Steps to Reproduce: 1.emerge python-2.6 2.run python-updater and unemerge any other versions 3.emerge mpich2-1.0.8 Actual Results: It won't be possible to execute mpiexec, mppboot, etc Python files will be installed into /usr/lib/python2 Expected Results: Should emerge properly with python-2.6 This problem most likely affects other mpich2 versions as well, but this was not tested. Was solved to me by passing --with-python=python${PYVER} to econf
Created attachment 191275 [details, diff] passes --with-python=python${PYVER} to econf should work after applying this
Fixed for 1.0.8 in cvs by patching mpd's configure. Thanks for reporting.
