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

When building Python on OS X, test whether _scproxy can be imported successfully. #21685

Closed
jhpalmieri opened this issue Oct 11, 2016 · 16 comments

Comments

@jhpalmieri
Copy link
Member

On OS X 10.12, and also with some earlier versions of OS X, we have had problems with the Sage build because Python claimed to build correctly even though the module _scproxy did not actually build. So let's test to make sure.

Component: packages: standard

Author: John Palmieri

Branch/Commit: 791ed00

Reviewer: François Bissey

Issue created by migration from https://trac.sagemath.org/ticket/21685

@jhpalmieri
Copy link
Member Author

Branch: u/jhpalmieri/test_scproxy

@jhpalmieri
Copy link
Member Author

New commits:

3fc278eWhen building Python on OS X, test whether _scproxy can be imported successfully.

@jhpalmieri
Copy link
Member Author

Commit: 3fc278e

@kiwifb
Copy link
Member

kiwifb commented Oct 11, 2016

comment:3

Is there a way to test before installing python? Once python is installed you are screwed, so it should happen before, or possibly start the clean up.

@jhpalmieri
Copy link
Member Author

comment:4

I don't know enough about the Python build process to know how to test before it is installed. We can uninstall if it fails, though.

@kiwifb
Copy link
Member

kiwifb commented Oct 11, 2016

comment:5

I'll look to see if there is an easy way to figure out before installing.

@kiwifb
Copy link
Member

kiwifb commented Oct 11, 2016

comment:6

From the "src" folder

find build -name _scproxy.so
build/lib.macosx-10.9-x86_64-2.7/_scproxy.so

So we should abort if find returns nothing before installing I'd say.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Oct 11, 2016

Branch pushed to git repo; I updated commit sha1. New commits:

2c4f43ctrac 21685: uninstall the Python if _scproxy does not import.

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Oct 11, 2016

Changed commit from 3fc278e to 2c4f43c

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Oct 11, 2016

Changed commit from 2c4f43c to 791ed00

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Oct 11, 2016

Branch pushed to git repo; I updated commit sha1. New commits:

791ed00trac 21685: detect whether _scproxy has built before installing.

@jhpalmieri
Copy link
Member Author

comment:9

Great, that's better than what I was doing. I'm wary of deleting things, so I've removed that part of my changes. I think we can still test for _scproxy at the end, just in case.

@jhpalmieri
Copy link
Member Author

comment:10

I just tested this on OS X 10.12 with and without my branch from #21567 (so with Python succeeding and failing to build _scproxy) and it seems to detect this correctly.

@kiwifb
Copy link
Member

kiwifb commented Oct 12, 2016

comment:11

Looks good to me.

@kiwifb
Copy link
Member

kiwifb commented Oct 12, 2016

Reviewer: François Bissey

@vbraun
Copy link
Member

vbraun commented Oct 29, 2016

Changed branch from u/jhpalmieri/test_scproxy to 791ed00

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

3 participants