jasonmolenda wrote:
I set aside my current work, updated to current main sources, cherry-picked
253c28fa829cee0104c2fc59ed1a958980b5138c, built it on my macOS system, did
`bin/lldb-dotest -p TestImportBuiltinFileID.py` and it crashes like before.
I'm not sure what you're asking help with, I do
Author: Jason Molenda
Date: 2024-05-21T18:04:38-07:00
New Revision: dfdf1c5fe45a82b9c578306f3d7627fd251d63f8
URL:
https://github.com/llvm/llvm-project/commit/dfdf1c5fe45a82b9c578306f3d7627fd251d63f8
DIFF:
https://github.com/llvm/llvm-project/commit/dfdf1c5fe45a82b9c578306f3d7627fd251d63f8.diff
jasonmolenda wrote:
I reverted in
```
commit dfdf1c5fe45a82b9c578306f3d7627fd251d63f8
Author: Jason Molenda
Date: Tue May 21 18:00:11 2024 -0700
Revert "[clang-repl] Extend the C support. (#89804)"
This reverts commit 253c28fa829cee0104c2fc59ed1a958980b5138c.
```
to unblock the
jasonmolenda wrote:
fwiw if you have access to a mac, I don't think it's hard to build lldb+clang?
I have swig, cmake, and ninja installed on my mac via homebrew.
```
lldb/scripts/macos-setup-codesign.sh
mkdir build
cd build
cmake ../llvm -G Ninja -DLLDB_ENABLE_SWIFT_SUPPORT=0
-DPython3_EXE