https://bugs.llvm.org/show_bug.cgi?id=39559
Vince Bridgers <vince.a.bridg...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |vince.a.bridg...@gmail.com
Resolution|--- |WORKSFORME
--- Comment #1 from Vince Bridgers <vince.a.bridg...@gmail.com> ---
I looked into this, and am not able to repro under currently documented build
environment. I was able to repro under very particular build/run environments,
so I suspect David encountered one or the other issue that leads to this
segfault. This problem can occur due to 1 of the following reasons:
1) LLVM compiler built with LLVM_ENABLE_PIC=on. There was a patch created to
disable Python bindings under these conditions at some point. Perhaps this was
the problem at the time.
2) Perhaps a problem with the Python version used - I'm guessing this was the
problem in the original report.
This problem has been reported a few times, and there have been different
approaches to addressing this. If a reader comes across this issue looking for
a solution, please look at those and also check out the following references.
References …
Python binding tests disabled when LLVM_ENABLE_PIC=OFF
https://lists.llvm.org/pipermail/cfe-commits/Week-of-Mon-20190114/257720.html
Appears to be caused by a regression in Python. See
https://bugs.python.org/issue37140
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
