Unable to see Python binary

[prabalrakshit]

BPO	1082874
Nosy	@loewis

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2005-01-06.20:31:23.000>
created_at = <Date 2004-12-10.12:26:54.000>
labels = ['invalid', 'expert-installation']
title = 'Unable to see Python binary'
updated_at = <Date 2005-01-06.20:31:23.000>
user = 'https://bugs.python.org/prabalrakshit'

bugs.python.org fields:

activity = <Date 2005-01-06.20:31:23.000>
actor = 'loewis'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Installation']
creation = <Date 2004-12-10.12:26:54.000>
creator = 'prabal_rakshit'
dependencies = []
files = []
hgrepos = []
issue_num = 1082874
keywords = []
message_count = 4.0
messages = ['23627', '23628', '23629', '23630']
nosy_count = 4.0
nosy_names = ['loewis', 'greg_ball', 'dyoo', 'prabal_rakshit']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1082874'
versions = ['Python 2.3']

[prabalrakshit]

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??

[dyoo]

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?

[gregball]

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.

[loewis]

Logged In: YES
user_id=21627

Most likely, "make install" was missing. Closing this report
as invalid.