William Moreno added the comment:
Thank's a lot by answered me, I am now at FreeBSD team in order to fix this
issue.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18008
___
William Moreno added the comment:
[SOLVED on FreeBSD 9.1] if anyone need to see
http://www.freshports.org/lang/python33/ thank's again to alls specyally to
Marcus von Appen (marcusva)
--
___
Python tracker rep...@bugs.python.org
New submission from William Moreno:
cc -DNDEBUG -O2 -pipe -fno-strict-aliasing -pthread -pthread Parser/acceler.o
Parser/grammar1.o Parser/listnode.o Parser/node.o Parser/parser.o
Parser/bitset.o Parser/metagrammar.o Parser/firstsets.o Parser/grammar.o
Parser/pgen.o
Ned Deily added the comment:
You did not provide enough information to determine exactly what went wrong in
your build but you are likely running in an environment with non-standard
permissions (umask, root, ACLs, etc.). Note that the failure occurs when the
main Makefile rule to build
Marcus von Appen added the comment:
This is a FreeBSD-specific problem with the Python 3.3 port. Using pmake (BSD's
make implementation) leads to random errors on either generating pgen or
executing pgen.
This seems to happen since Python 3.3.1 randomly and is quite hard to
reproduce.
Ned Deily added the comment:
I don't know of an intention to break use of other makes but I don't know of
any specific effort to test with various makes. As you may have noticed, there
were some significant changes to the Makefile rules for pgen-related targets by
changeset 52597f888e7a
Georg Brandl added the comment:
Indeed, the new hg touch facility should have been integrated in the release
script.
I've done that now, in the future all necessary files should have the correct
timestamps in the release tarballs.
--
resolution: works for me - fixed
status: open -
