-
Notifications
You must be signed in to change notification settings - Fork 768
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
[READY] Test python 3.3 on OS X #363
Conversation
Reviewed 3 of 3 files at r1. ci/travis/travis_install.osx.sh, line 8 [r1] (raw file):
Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 1 unresolved discussion. ci/travis/travis_install.osx.sh, line 8 [r1] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 1 unresolved discussion. ci/travis/travis_install.osx.sh, line 8 [r1] (raw file): you have to edit your comments on gihub :) what about this: # List of homebrew formulae to install in the order they appear"
REQUIREMENTS="node.js
go
ninja
readline
autoconf
pkg-config
openssl
pyenv"
# install node, go, ninja, pyenv and dependencies
for pkg in $REQUIREMENTS; do
# install package, or upgrade it if it is already installed
brew install $pkg || brew outdated $pkg || brew upgrade $pkg
done Comments from the review on Reviewable.io |
Reviewed 3 of 3 files at r1. build.py, line 159 [r1] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 2 unresolved discussions. build.py, line 159 [r1] (raw file): Comments from the review on Reviewable.io |
Review status: all files reviewed at latest revision, 2 unresolved discussions. ci/travis/travis_install.osx.sh, line 8 [r1] (raw file): Comments from the review on Reviewable.io |
Review status: 1 of 3 files reviewed at latest revision, 4 unresolved discussions. build.py, line 164 [r1] (raw file): ci/travis/travis_install.osx.sh, line 14 [r1] (raw file): Seems like we should be able to use upstream (that is, non-brew) pyenv on both platforms. ci/travis/travis_install.osx.sh, line 40 [r1] (raw file): Comments from the review on Reviewable.io |
Review status: 1 of 3 files reviewed at latest revision, 3 unresolved discussions. ci/travis/travis_install.osx.sh, line 14 [r1] (raw file): ci/travis/travis_install.osx.sh, line 40 [r1] (raw file): Comments from the review on Reviewable.io |
OK i have refactored out the pyenv stuff and it is all good ;) Appveryor is not working, but i don't think i could possibly have broken that :) Review status: 1 of 5 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed. Comments from the review on Reviewable.io |
Review status: 1 of 5 files reviewed at latest revision, 3 unresolved discussions, some commit checks failed. ci/travis/travis_install.osx.sh, line 8 [r1] (raw file): ci/travis/travis_install.osx.sh, line 14 [r1] (raw file): ci/travis/travis_install.osx.sh, line 40 [r1] (raw file): Comments from the review on Reviewable.io |
☔ The latest upstream changes (presumably f263af2) made this pull request unmergeable. Please resolve the merge conflicts. |
Thanks for doing this! :) Not triggering homu because it's saying this has merge conflicts (otherwise I would). Review status: 1 of 5 files reviewed at latest revision, 1 unresolved discussion, some commit checks failed. Comments from the review on Reviewable.io |
…s ensuring that python is built with a shared library
91ebf08
to
5f52f25
Compare
I have rebased on your PR. Review status: 1 of 5 files reviewed at latest revision, 1 unresolved discussion. Comments from the review on Reviewable.io |
[READY] Test python 3.3 on OS X
Thanks! |
Force the use of dynamically linked python on OS X
On OS X, Python and all of its extension libraries must be built using the same shared python library. If any of them contain a statically linked libpython.a, then the global variable linkage gets broken, and you are presented with an obscure crash. We force users to link against a dynamically linked python.
Fixes ycm-core/YouCompleteMe#18 (comment).
Testing
Pyenv works fine if you specify the
--enable-framework
at build time (as noted above).Also, the virtualenv bug is fixed, so bump the version to latest.