- User Since
- Jul 8 2019, 3:25 PM (119 w, 5 d)
Aug 20 2019
Thank you! I am not a committer, could one of you land this?
Ping? I think this version is a good compromise that will work well both for binary distributions and compiling from source...
Aug 16 2019
I'm not sure that such a python3 vs 3.5 difference matters, but anyway, here's a version that does arguably the right thing.
Use python's basename
It actually worked with the env for me.
Aug 8 2019
Aug 5 2019
Should this be merged to LLVM 9?
Jul 18 2019
Preferring Python 3, if present, was actually intentional on my behalf on the basis that we should use the newer Python if we can. But I did not realize this would break MacOS :( (and, it sounds like, any system where you have a python 3 binary but not devel package?)
Jul 17 2019
pree-jackie: My guess is that you have python2.7-dev installed but not python3.6-dev -- does it work if you install that one?
Jul 12 2019
Thanks! Could you/someone land this? I'm not a committer.
How about this, then? It does seem to work.
Move the version list outside of the strequal "" check
Jul 11 2019
Yes, this does not seem to be used when building as part of LLVM, only standalone.
Match LLVM and remove the line from LLDBStandalone
Jul 10 2019
Yeah. (I thought I did? I'm not super familiar with this interface)
Thanks Greg! I'm not a committer -- how do I get this committed?
Jul 9 2019
Add 3.7 and 3.5
Ah, this works because Swig (?) adds compatibility macros to LLDBWrapPython:
#define PyInt_Check(x) PyLong_Check(x)
#define PyInt_AsLong(x) PyLong_AsLong(x)
#define PyInt_FromLong(x) PyLong_FromLong(x)
#define PyInt_FromSize_t(x) PyLong_FromSize_t(x)
Jul 8 2019
It seems this wasn't necessary, I had just misconfigured my build. (I don't understand how this works though...)