➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: Unable to see Python binary
Type: Stage:
Components: Installation Versions: Python 2.3
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: dyoo, greg_ball, loewis, prabal_rakshit
Priority: normal Keywords:

Created on 2004-12-10 12:26 by prabal_rakshit, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Messages (4)
msg23627 - (view) Author: Prabal Rakshit (prabal_rakshit) Date: 2004-12-10 12:26 
After extracting the Python-2.3.3.tar we could get the 
appropriate folder structure. 
We then executed the configure script. Therafter when 
we execute the make command the Python binary is not 
created in /usr/local/bin.

Any pointers??
msg23628 - (view) Author: Danny Yoo (dyoo) Date: 2004-12-10 21:19 
Logged In: YES 
user_id=49843

The 'make install' target will copy the built binary to
'/usr/local/bin'.  Did you try 'make install' yet?
msg23629 - (view) Author: Gregory H. Ball (greg_ball) Date: 2004-12-13 15:45 
Logged In: YES 
user_id=11365

Are you running "make install" after "make" ?

You could try explicitly giving an installation prefix:

./configure --prefix=/usr/local

Otherwise you can look for newly created files like this:

find /usr -mmin -5

Hope this helps.
msg23630 - (view) Author: Martin v. Löwis (loewis) * (Python committer) Date: 2005-01-06 20:31 
Logged In: YES 
user_id=21627

Most likely, "make install" was missing. Closing this report
as invalid.
History
Date User Action Args
2022-04-11 14:56:08adminsetgithub: 41304
2004-12-10 12:26:54prabal_rakshitcreate