Message 116448 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	belopolsky
Recipients	belopolsky
Date	2010-09-15.14:08:12
SpamBayes Score	6.583909e-07
Marked as misclassified	No
Message-id	<[email protected]>
In-reply-to

Content
When testing config options, it is often useful to build python in a directory different from the root of the source tree. This is supported by autoconf based builds as follows: you cd to the desired directory run configure with an explicit path. For example: $ cd ../altdir $ ../python-source/configure $ make However, this fails for python 3.1 and 3.2 with the following error: i686-apple-darwin10-gcc-4.2.1: Parser/tokenizer_pgen.o: No such file or directory i686-apple-darwin10-gcc-4.2.1: Parser/printgrammar.o: No such file or directory i686-apple-darwin10-gcc-4.2.1: Parser/pgenmain.o: No such file or directory make: *** [Parser/pgen] Error 1

When testing config options, it is often useful to build python in a directory different from the root of the source tree.  This is supported by autoconf based builds as follows: you cd to the desired directory run configure with an explicit path. For example:

$ cd ../altdir
$ ../python-source/configure
$ make

However, this fails for python 3.1 and 3.2 with the following error:


i686-apple-darwin10-gcc-4.2.1: Parser/tokenizer_pgen.o: No such file or directory
i686-apple-darwin10-gcc-4.2.1: Parser/printgrammar.o: No such file or directory
i686-apple-darwin10-gcc-4.2.1: Parser/pgenmain.o: No such file or directory
make: *** [Parser/pgen] Error 1

History
Date	User	Action	Args
2010-09-15 14:08:16	belopolsky	set	recipients: + belopolsky
2010-09-15 14:08:15	belopolsky	set	messageid: <[email protected]>
2010-09-15 14:08:13	belopolsky	link	issue9860 messages
2010-09-15 14:08:12	belopolsky	create