Re: [lldb-dev] [Release-testers] [11.0.0 Release] Release Candidate 1 is here
On Tue, 2020-07-28 at 19:49 +0200, Hans Wennborg via Release-testers wrote: > Hello everyone, > > We're a little bit behind schedule, but RC1 is now here. It was tagged > earlier today as llvmorg-11.0.0-rc1. > > Source code and docs are available at > https://prereleases.llvm.org/11.0.0/#rc1 and > https://github.com/llvm/llvm-project/releases/tag/llvmorg-11.0.0-rc1 > > Pre-built binaries will be added as they become available. > > Please file bug reports for any issues you find as blockers of > https://llvm.org/pr46725 > > Release testers: please start your engines, run the script, share your > results, and upload binaries. > On Gentoo: - clang fails to build due to using internal llvm headers, bug filed. - openmp needs backport from master, also filed. - lldb tests are still broken, still had no time to look at them. - compiler-rt started failing on GotsanCheck after switching to new build machine, I'm trying to figure it out right now. -- Best regards, Michał Górny signature.asc Description: This is a digitally signed message part ___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
[lldb-dev] [Bug 46891] New: "import _lldb" doesn't work on Windows with Python 3.8+
https://bugs.llvm.org/show_bug.cgi?id=46891 Bug ID: 46891 Summary: "import _lldb" doesn't work on Windows with Python 3.8+ Product: lldb Version: unspecified Hardware: All OS: Windows NT Status: NEW Severity: normal Priority: P Component: All Bugs Assignee: lldb-dev@lists.llvm.org Reporter: tatyana.krasnu...@synopsys.com CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org This happens when liblldb.dll depends on non-system libraries (e.g. libxml2.dll). To reproduce this issue, build LLDB with LibXML2 and run `python_d -c "import _lldb"`. The error will be "ImportError: DLL load failed while importing _lldb: The specified module could not be found". Neither PATH nor PYTHONPATH makes a difference. Since version 3.8, Python stopped searching dlls in directories specified by PATH. Now such paths should be specified by calling `add_dll_directory()` (https://docs.python.org/3.8/whatsnew/3.8.html#bpo-36085-whatsnew). Seems like the function call should be placed in bindings/python.swig right before importing _lldb, however, I don't see a way to determine paths to dependencies there. -- You are receiving this mail because: You are the assignee for the bug.___ lldb-dev mailing list lldb-dev@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
