i changed my default python version to 3.4 recently because Python2.7 will became obsolete in some month, and Python 3.5 was released.
I noticed it's impossible to build LLVM 3.7 with Python 3.4 whereas LLVM 3.6 builds properly. I think there is a missing 2to3 in the build process but i don't know how to solve the problem.
[2783/3812] Linking CXX static library lib/liblldbBase.a
[2784/3812] Python script building LLDB Python wrapper
FAILED: cd /wrkdirs/usr/ports/devel/llvm37/work/.build/tools/lldb/scripts && /usr/local/bin/python3.4 /wrkdirs/usr/ports/devel/llvm37/work/llvm-3.7.0.src/tools/lldb/scripts/buildSwigWrapperClasses.py --srcRoot=/wrkdirs/usr/ports/devel/llvm37/work/llvm-3.7.0.src/tools/lldb --targetDir=/wrkdirs/usr/ports/devel/llvm37/work/.build/tools/lldb/scripts --cfgBldDir=/wrkdirs/usr/ports/devel/llvm37/work/.build/tools/lldb/scripts --prefix=/wrkdirs/usr/ports/devel/llvm37/work/.build --swigExecutable=/usr/local/bin/swig -m
File "/wrkdirs/usr/ports/devel/llvm37/work/llvm-3.7.0.src/tools/lldb/scripts/buildSwigWrapperClasses.py", line 129
Can you fix it please ?
A commit references this bug:
Date: Mon Oct 19 23:34:21 UTC 2015
New revision: 399795
Add an option to build extra clang tools.
Add an insufficient set of patch toward building when the default python
is python 3. Scripts now run, but lldb uses APIs that have been
removed in C code.
Some small changes aimed at reducing future plist churn.
Upstream LLVM doesn't yet support python 3. There is basically no chance they will ever support python 3 for any shipped release including 3.7 and probably 3.8.