Ned Deily added the comment:
I believe there are two different issues here. One: since the python-dev switch
to hg, Python source release tarballs no longer have had consistent file time
stamps which result in unnecessary generation steps being run in a build.
Python 2.7 and 3.3 now include
pfg added the comment:
The problem is Makefile.pre.in was changed in a way that stops out-of-tree
builds.
The following patch by Markus Von Appen fixes it.
--
status: closed - open
Added file: http://bugs.python.org/file29736/patch-Makefile.pre.in
pfg added the comment:
Ruslan Makhmatkhanov provided this (more complete) patch.
--
Added file: http://bugs.python.org/file29737/patch-Makefile.pre.in
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17649
Changes by pfg giffu...@tutopia.com:
Removed file: http://bugs.python.org/file29736/patch-Makefile.pre.in
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17649
___
Ramchandra Apte added the comment:
if the Python/Python-ast.c file does not exist in the Python source directory,
try re-extracting it (if the file still doesn't exist then you probably have a
corrupt compressed file)
--
nosy: +Ramchandra Apte
___
Ned Deily added the comment:
Python-ast.c is a generated file. As released, a Python source tarball should
contain an up-to-date version that does not need to be regenerated. However, if
the timestamps of the source files are not preserved, the Makefile may think it
is out of date and try to
pfg added the comment:
I looked and the file exists:
$ file Python/Python-ast.c
Python/Python-ast.c: C source, ASCII text
The file appears valid.
I touched the files as suggested but I still I get the same error message when
running configure.
FWIW, the Makefile.pre.in target exists but it
pfg added the comment:
Correction:
The problem does arise during the build process (not configure).
Still specifying the touch target for the build or touching manually the files
doesn't help :(
--
___
Python tracker rep...@bugs.python.org
Ned Deily added the comment:
I'm afraid it's not likely we'll be able to further resolve this issue without
more specific information about exactly the steps you are using to try to build
Python, including exactly what version or hg rev id (you say 2.7.2 but the path
name says 2.7.4), any
pfg added the comment:
Oops.. I am sorry I reported the wrong version,
I am using python-2.7.4 just released
SHA256 (python/Python-2.7.4.tar.xz) =
b6626eb6d07d72351f251116ab14427fc934b5f24e6ebc751356a44a7d23b62d
SIZE (python/Python-2.7.4.tar.xz) = 10250644
And I am running something similar
New submission from pfg:
This happens when I run configure for python 2.7.2 on FreeBSD
...
cc -c -fno-strict-aliasing -O2 -fno-strict-aliasing -pipe -march=nocona
-DNDEBUG -O2 -fno-strict-aliasing -pipe -march=nocona -I. -IInclude
-I./../Include -fPIC -DPy_BUILD_CORE -o Python/Python-ast.o
11 matches
Mail list logo