Minor problem with ‘make install/altinstall’ and multiprocessing.

June 19th, 2008 § 2 comments

Looks like I missed a spot when adding in the pack­age, and if you do a ‘make install’ or make altin­stall (which I never do — sorry about that) the pack­age is missing.

See the bug report for more infor­ma­tion and a small patch. Make­files for the win.

As a side note — I do not rec­om­mend peo­ple do a make install into the the sys­tem path on their machines. It’s gen­er­ally poor form to do that with alphas/betas/trunks. If any­thing, just do a make, and the add a sym­bolic link in /usr/bin or wher­ever point­ing to the python binary in the source directory.

Of course, I’m so anal about sys­tem paths I use virtualenv.py a *lot*. Of course, if I was ‘make installing’ a lot I would have found this. /grumble

  • http://www.aleax.it Alex Martelli

    What “sys­tem path”? ‘make install’ puts python in /usr/local/bin and doesn’t dis­turb the sys­tem instal­la­tion, which is /usr/bin — at least that’s how I’ve always seen it work.

  • http://www.aleax.it Alex Martelli

    What “sys­tem path”? ‘make install’ puts python in /usr/local/bin and doesn’t dis­turb the sys­tem instal­la­tion, which is /usr/bin — at least that’s how I’ve always seen it work.

What's this?

You are currently reading Minor problem with ‘make install/altinstall’ and multiprocessing. at jessenoller.com.

meta