wlav
wlav
The error message as posted in the other report is independent of CUDA, right? In which case it has to be an environment mixup with the PCH needing rebuilding. I'd...
Closing as clarified.
Specific error is here: ``` src/CPyCppyy.h:35:10: fatal error: Python.h: No such file or directory 35 | #include "Python.h" ``` Apparently, you don't have the Python C-API headers installed. (You can...
I understand neither the problem, nor the proposed solution, but at issue is likely that the backend is split into two PyPI packages, a large one containing Cling and a...
Yes, upstream has also been asking for a cleanup. There could be a top-level `setup.py` to combine the two (both packages are sitting in the same repo already; upstream even...
cppyy 3.x uses Clang13. I don't think there's an issue with supporting 11.8 per se, but Clang has a bunch of places in its `Cuda.cpp` where it hard-wires various versions....
Firstly, dictionaries may not give you the hoped for speed-up. Upstream has been touting modules for the longest time, but after never quite pulling it off (or getting the promised...
Ouch. But I don't understand ... `ExecAutoParse` does not call `removeDecl`? I don't see any call to `removeDecl` in any of Cling's parsing functions. (It may be inlined from someplace...
Sounds good. The relative headers is purely to allow redistribution of binaries. Yes, they then got resolved, so makes sense that `ExecAutoParse` sees absolute paths.