Building python-svn from source

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • The Pythonista

    Building python-svn from source

    First of all, I apologize if this would be more appropriate for python-
    dev, but I don't normally subscribe to that list, and felt it would also
    be of general use, so....

    I'm having problems building the latest Python 2.6 and 3.0 from
    subversion, and I'm not sure how to resolve the problem. In each case,
    configure executes without problem, but, when I execute 'make', I get
    this error (the same one for both 2.6 and 3.0):

    ../Parser/asdl_c.py -h ./Include ./Parser/Python.asdl
    Must specify exactly one output file
    make: *** [Include/Python-ast.h] Error 1

    Am I doing something wrong? If not, how do I work around this error?

    Thanks!

    --
    code.py: A blog about life, the universe, and Python

    A blog about life, the universe, and Python.

    ** Posted from http://www.teranews.com **
  • =?UTF-8?B?Ik1hcnRpbiB2LiBMw7Z3aXMi?=

    #2
    Re: Building python-svn from source

    ./Parser/asdl_c.py -h ./Include ./Parser/Python.asdl
    Must specify exactly one output file
    make: *** [Include/Python-ast.h] Error 1
    >
    Am I doing something wrong? If not, how do I work around this error?
    For some reason, the getopt module in your host's python cannot process
    the command line options to asdl_c.py correctly.

    What Python version do you have installed in PATH?

    In any case, just touch Include/Python-ast.h and Python/Python-ast.c
    before building, to work around this issue.

    Regards,
    Martin

    Comment

    • The Pythonista

      #3
      Re: Building python-svn from source

      On Tue, 12 Aug 2008 07:04:41 +0200, Martin v. Löwis wrote:

      For some reason, the getopt module in your host's python cannot process
      the command line options to asdl_c.py correctly.
      >
      What Python version do you have installed in PATH?
      Martin,

      Thank you so much! In fact, I did have a python executable on my PATH in
      ~/bin that was screwing things up. After I moved it (thus leaving the
      system default python as the only python executable on my PATH), the
      build process went smoothly (except for not being able to find a few
      libraries for some C extensions, but I think I can fix that).

      I now have working python2.6 and python3.0 executables to play with,
      thanks to you. :-)
      --
      code.py: A blog about life, the universe, and Python

      A blog about life, the universe, and Python.

      ** Posted from http://www.teranews.com **

      Comment

      Working...