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: fix python_finder: prefer python2, look for/prefer .so #55

Closed
wants to merge 2 commits into from

Conversation

blueyed
Copy link

@blueyed blueyed commented Nov 19, 2014

This fixes building YCM / ycmd for pyenv with python3 and python2
activated/configured.

@vheon
Copy link
Contributor

vheon commented Nov 19, 2014

Travis is not happy

@blueyed
Copy link
Author

blueyed commented Nov 19, 2014

That's a flake8 error for the testdata files.

It seems to be unrelated to this PR, isn't it?

@blueyed blueyed mentioned this pull request Nov 19, 2014
# So we are forced to do its job for it.
python_prefix=$(python-config --prefix | sed 's/^[ \t]*//')
# Prefer python2-config over python-config.
hash python2-config 2>/dev/null && python_config=python2-config \
Copy link
Member

Choose a reason for hiding this comment

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

It seems you want to use command_exists, which is declared in this file.

@blueyed blueyed force-pushed the fix-build-python-config branch 3 times, most recently from b41a5af to 0caf357 Compare November 19, 2014 21:58
@Valloric
Copy link
Member

You need to state did you sign the Google CLA.

@Valloric
Copy link
Member

Also, why should we prefer the .so version of the .a?

This fixes building YCM / ycmd for pyenv with python3 and python2
activated/configured.
I had a `.rej` file from `patch` for a submodule, and
check_third_party_libs complained about it.
@blueyed
Copy link
Author

blueyed commented Nov 27, 2014

Also, why should we prefer the .so version of the .a?

I am not sure and remember it not completely anymore. It is probably related to first installing python without --enable-shared, then with this option and not removing the .a file..?!
(Ref: pyenv/pyenv#65).

You need to state did you sign the Google CLA.

No.

@vheon
Copy link
Contributor

vheon commented Nov 27, 2014

No.

You can't push anything to the repo if you do not sign the Google CLA.

@Valloric
Copy link
Member

You need to state did you sign the Google CLA.

No.

Then please don't send pull requests!

@Valloric Valloric closed this Nov 30, 2014
@blueyed blueyed deleted the fix-build-python-config branch November 30, 2014 23:19
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.

3 participants