Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build of python 2.5 failed with subversion on Archlinux #14

Closed
Azd325 opened this issue Apr 22, 2013 · 9 comments
Closed

Build of python 2.5 failed with subversion on Archlinux #14

Azd325 opened this issue Apr 22, 2013 · 9 comments

Comments

@Azd325
Copy link

Azd325 commented Apr 22, 2013

I'm trying to install 2.5.6 and will dont work.
Maybe has to do with this http://superuser.com/questions/564118/error-compiling-python-2-7-3-on-centos5

tim@localhost ~ % pyenv install 2.5.6
Downloading Python-2.5.6.tar...
-> http://www.python.org/ftp/python/2.5.6/Python-2.5.6.tgz
Installing Python-2.5.6...

BUILD FAILED

Inspect or clean up the working tree at /tmp/python-build.20130422153800.5017
Results logged to /tmp/python-build.20130422153800.5017.log

Last 10 log lines:
Parser/pgen ./Grammar/Grammar ./Include/graminit.h ./Python/graminit.c
mkdir: cannot create directory ‘Include’: File exists
make: [Python/graminit.c] Error 1 (ignored)
Parser/pgen ./Grammar/Grammar ./Include/graminit.h ./Python/graminit.c
gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I'/home/tim/.pyenv/versions/2.5.6/include' -DPy_BUILD_CORE -o Python/compile.o Python/compile.c
gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I'/home/tim/.pyenv/versions/2.5.6/include' -DPy_BUILD_CORE -o Python/graminit.o Python/graminit.c
gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I'/home/tim/.pyenv/versions/2.5.6/include' -DPy_BUILD_CORE -o Python/symtable.o Python/symtable.c
gcc -pthread -c -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -Wstrict-prototypes -I. -IInclude -I./Include -I'/home/tim/.pyenv/versions/2.5.6/include' -DPy_BUILD_CORE -DSVNVERSION="LC_ALL=C svnversion ." -o Modules/getbuildinfo.o ./Modules/getbuildinfo.c
gcc: error: directory": No such file or directory
make: *** [Modules/getbuildinfo.o] Error 1

Do you have any ideas?

@yyuu
Copy link
Contributor

yyuu commented Apr 22, 2013

What is your operating system? I can build 2.5.6 on my Debian sid box without troubles.

@Azd325
Copy link
Author

Azd325 commented Apr 22, 2013

I have an Arch Linux
2.7.4 and 2.6.6 are also working for me but the whole 2.5 row not

@Azd325
Copy link
Author

Azd325 commented Apr 22, 2013

Do you want to have my complete error log?

@yyuu
Copy link
Contributor

yyuu commented Apr 22, 2013

This seems to be a problem of python build process, not a problem of pyenv.

Because the problem is not reproduced on my machine, basically, please find the cause of the trouble by yourself. I'll try to setup Arch Linux as VM, but I cannot promise you anything about this trouble.

@yyuu
Copy link
Contributor

yyuu commented Apr 25, 2013

I tested building CPython 2.5.6 on latest Arch Linux (cleanly installed), and it finishes without any problems. After that, I did sudo pacman -S subversion and then try rebuilding, it fails by the same error as yours.

@Azd325
Copy link
Author

Azd325 commented Apr 25, 2013

Yep. I have subversion installed.
Is the subversion version to high?

@Azd325
Copy link
Author

Azd325 commented Apr 25, 2013

Or what can be the reason?

@yyuu
Copy link
Contributor

yyuu commented Apr 25, 2013

The Python build system expects svnversion to print "exported" if the source tree is not on the Subversion repository. But recent version of Suversion prints "Unversioned directory" in place of "exported". This is the why build fails.

Just placing following script as svnversion into your $PATH will solve the build problem.

#!/bin/sh
echo exported

Other workarounds described in the post you pointed are also effective.

Again, this is not a kind of problem of pyenv.

@Azd325
Copy link
Author

Azd325 commented Apr 25, 2013

But thanks for the help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants