specify which python-config, fixes undefined symbol #4
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi. Thank you so much for your contribution! |
belltailjp
added a commit
that referenced
this pull request
Aug 3, 2015
specify which python-config, fixes undefined symbol
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think this fixes #2 and #3. I had the same issue (undefined symbol when
import segment).The command
python-config, by default, returns info for python2.7... specifying forpython3.4-configprovides the proper flags and whatnot. The segment.so file was compiling fine, just with the wrong linked libraries (python2)...I'm not sure if this change is ideal, but at least this PR documents how to fix it...
Thanks for the code.