Skip to content

Fix bug in igraph recipe #177

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

Merged
merged 4 commits into from
Dec 8, 2013
Merged

Fix bug in igraph recipe #177

merged 4 commits into from
Dec 8, 2013

Conversation

clayote
Copy link
Contributor

@clayote clayote commented Nov 29, 2013

igraph was failing to build when the build machine (x64) had its own igraph libraries. setup.py links against stuff in /usr/local/lib by default. Now I've patched it so it doesn't.

…or a non-ARM achitecture.

Also, get_platform.py was never really used. I thought I'd need to know exactly how distutils wanted me to write the architecture name, but I didn't really.
@clayote
Copy link
Contributor Author

clayote commented Nov 29, 2013

Please pull again, I fixed a bug

@@ -29,6 +29,8 @@ function shouldbuild_igraph() {

function build_igraph() {
cd $BUILD_igraph
patch setup.py $RECIPE_igraph/setup.py.patch
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

normally, the patch is done is the prebuild phase, as the build be recalled later, so double-patch will not work. Do another PR for that please :)

tito added a commit that referenced this pull request Dec 8, 2013
@tito tito merged commit c87a33c into kivy:master Dec 8, 2013
@clayote
Copy link
Contributor Author

clayote commented Dec 8, 2013

In my testing, the prebuild phase never actually executed. Could I get some clarification on when it happens?

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

Successfully merging this pull request may close these issues.

2 participants