Build requires already built Python

[sdeibel]

BPO	1469548

^{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 2006-04-13.02:18:57.000>
created_at = <Date 2006-04-12.23:54:18.000>
labels = ['build']
title = 'Build requires already built Python'
updated_at = <Date 2006-04-13.02:18:57.000>
user = 'https://bugs.python.org/sdeibel'

bugs.python.org fields:

activity = <Date 2006-04-13.02:18:57.000>
actor = 'anthonybaxter'
assignee = 'none'
closed = True
closed_date = None
closer = None
components = ['Build']
creation = <Date 2006-04-12.23:54:18.000>
creator = 'sdeibel'
dependencies = []
files = []
hgrepos = []
issue_num = 1469548
keywords = []
message_count = 2.0
messages = ['28210', '28211']
nosy_count = 2.0
nosy_names = ['anthonybaxter', 'sdeibel']
pr_nums = []
priority = 'normal'
resolution = 'accepted'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue1469548'
versions = ['Python 2.5']

[sdeibel]

On RedHat 7.1 I ran into the following interesting
build bug:

$ ./configure
(works fine)
$ make
./Parser/asdl_c.py -h ./Include -c ./Python
./Parser/Python.asdl
  File "./Parser.asdl_c.py", line 56
    j += 2 # account or the brase and space after it
       ^
SyntaxError: invalid syntax

This is because Python 1.5.2 is the default there --
OK, no problem working around that 'cause I've got
other versions there but it seems mighty strange that
the very first thing done in a build of Python requires
an already-built Python. What happens on an OS where
Python isn't there yet at all?

[anthonybaxter]

Logged In: YES
user_id=29957

This is a packaging bug. You can workaround it with 'touch
Python/Python-ast.c Python/Python-ast.h' before running make.