On Thursday 26 Nov 2015 09:29 CET, Steven D'Aprano wrote: > On Thursday 26 November 2015 18:00, Cecil Westerhof wrote: > >> On Wednesday 25 Nov 2015 23:58 CET, Laura Creighton wrote: >> >>> In a message of Wed, 25 Nov 2015 22:52:23 +0100, Cecil Westerhof >>> writes: >>>> >>>> My system python was all-ready damaged: that is why I wanted to >>>> build myself. >>> >>> Your Suse system probably wants to use python for something. If >>> your system python is damaged, you badly need to fix that, using >>> the system package managers tools, before Suse does some sort of >>> update on you, using the broken python, which damages more of your >>> system. >> >> I tried that. But it installs only things in /usr/lib and >> /usr/lib64, nothing in /usr/bin, but at the same time it is adamant >> that it installed python. I wanted a quick fix, but it looks like >> that is not going to work. :'-( I'll have to find a way to get >> things fixed. >> > > On the assumption that you are more interested in fixing your broken > system than learning how to compile Python, what happens if you use > the Suse package manager to re-install Python? > > e.g. zypper python
It installs things in /usr/lib and /usr/lib64, but nothing in /usr/bin. So it installs libraries, but not programs. By the way: I am of-course most interested to fix my system, but I would not mind to have python compiled also, so I (can) work with the latest stable version. ;-) -- Cecil Westerhof Senior Software Engineer LinkedIn: http://www.linkedin.com/in/cecilwesterhof -- https://mail.python.org/mailman/listinfo/python-list