cyphesis can't be build with python 2.7

Bug #674179 reported by Piotr
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cyphesis
Status tracked in Trunk
Trunk
Fix Released
Medium
Al Riddoch

Bug Description

I can't build cyphesis with python2.7 configure script returns error(Cannot find python headers for Python 2.2 or later).
Simple string replace in configure.ac from 2.6->2.7 don't help.

Al Riddoch (alriddoch)
Changed in cyphesis:
assignee: nobody → Al Riddoch (alriddoch)
importance: Undecided → Medium
status: New → Confirmed
milestone: none → 0.5.25
Revision history for this message
Al Riddoch (alriddoch) wrote :

Can you try the patch below which should add 2.7 to the list of versions it checks for?

If it doesn't work can you let me know the specific error you are getting, and attach a copy of your config.log to this bug? Please also include details of the OS you are building on.

Revision history for this message
Piotr (elminister) wrote :

Now configure script is executing properly.
But compilation process throws an error.

Builded with python 2.7.3
OS: archlinux
gcc: latest
cyphesis version: downloaded a few minutes ago from via git.

make log in attachment

Revision history for this message
Al Riddoch (alriddoch) wrote :

This error is unrelated to Python.

Current cyphesis git head needs latest Mercator git head to build as there is a new feature in development.

Please let me know if you fix the issue by using Mercator git head so I know whether to commit the Python fix.

Revision history for this message
Piotr (elminister) wrote :

Ok issue with mercator fixed. New errors however.

Revision history for this message
Piotr (elminister) wrote :
Revision history for this message
Al Riddoch (alriddoch) wrote :

I'm not sure what is going on there. Can you send me a translation of the error message: "Okrężna dyrektywa buildid.cpp <- buildid.cpp porzucona"

It may just be a warning about circular dependencies, but I need to check. Can you also attach the server/buildid.cpp file from your build to this bug? Can you also make sure your build log captures the full commandline for the step that fails, not just the stderr output. It's hard to tell but I think your log only includes stderr.

Revision history for this message
Piotr (elminister) wrote :

Okreżna dyrektywa buildid.cpp <- buildid.cpp przucona circular
translation:
 directive buildid.cpp <- buildid.cpp abandoned / left alone.

So your guess was correct.

Revision history for this message
Piotr (elminister) wrote :

this is the stout for build.log

make[2]: Okrężna dyrektywa buildid.cpp <- buildid.cpp porzucona.
Getting GIT buildid from number of ChangeLog commits
/usr/bin/env: python: Nie ma takiego pliku ani katalogu
make[2]: *** [buildid.cpp] Błąd 127
make[2]: *** Oczekiwanie na niezakończone zadania....
make[1]: *** [all-recursive] Błąd 1
make: *** [all] Błąd 2

Nie ma takiego pliku ani katalogu- there is no such file or directory
Błąd = error
Oczekiwanie na niezakończone zadania...= waiting for not-finished tasks
I don't attach buildid.cpp beacause it is blank.

Revision history for this message
Piotr (elminister) wrote :

Ok i know why there is a message /usr/bin/env: python: Nie ma takiego pliku ani katalogu
in my OS (archlinux) there are 3 python packaged:
python (python2.6 with executable named python)
python2 (python2.7 with exec named python2)
python3(obvious)
i maked the symlink /usr/bin/python to /usr/bin/python2 executable and now bugs are diffirent

Revision history for this message
Al Riddoch (alriddoch) wrote :

The errors you are now getting are the same as earlier. You need to remove the empty buildid.cpp file that was created when the script could not find python, and allow the build to generate a new one.

Revision history for this message
Piotr (elminister) wrote :

success

Revision history for this message
Al Riddoch (alriddoch) wrote :

Hooray!

I'll apply the patch to the master branch tomorrow, and it'll be included in the next release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.