Python 2.7.4 Released (but I had touble updating the port)

[Ruslan Makhmatkhanov]

Pedro F. Giffuni wrote on 08.04.2013 08:08:
> Hello guys;
>
> There is a new bugfix release in the 27 series with hundreds of
> bugfixes:
> http://hg.python.org/cpython/file/9290822f2280/Misc/NEWS
>
> I gave a try at updating the python27 port and it was rather easy to
> get started (almost all patches apply cleanly) but I get this problem
>   when building:
>
> ...
> 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
> Python/Python-ast.c
> cc: Python/Python-ast.c: No such file or directory
> cc: No input files specified
> *** [Python/Python-ast.o] Error code 1
>
> The file actually exists.
>
> I went ahead and reported the issue upstream (Issue17649) but it is
> irreproducible in their buildbot and the problem is not really theirs:
> it looks like the hacks that we do to stop some modules from building
> and the environment used to build the code out-of-tree don't get along
> very well.
>
> Perhaps someone here knows the port well enough to provide a fix?
> I guess it should be possible to modify the makefile to skip generating
> that file since it exists already but that's not very clean ;).
>
> Regards,
>
> Pedro.

As Marcus already said, the problem in changed path to AST_C_DIR (I also 
changed AST_H_DIR in the same way).

Here is the updated version by the way (pkg-plist changes is not yet 
included):
https://github.com/mexicarne/newpython/commit/7f03049da6883f1eb145a73e83c73be5fd6378a5


-- 
Regards,
Ruslan

Tinderboxing kills... the drives.