-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile-from-source failure, drawing on 3.0.0 from PyPI #198
Comments
Then where does this lib I also really don't understand the error. It seems to suggest that
and:
show? As for the gcc12 warnings; I'm working on them atm.; there's a simple fix in ROOT. |
Also to add, nothing in cppyy is going to look for |
gcc12 warnings have been mostly fixed in repo. |
The gcc12 issues should all be good now with release 3.1.0. Feel free to reopen if you find otherwise. |
cppyy 3.1.0: Fantastic! I'll check it out. (Sorry that I haven't gotten back to this, but when I do, I'll do a second test on a virtual machine that has never had ROOT on it.) |
I confirm that cppyy 3.1.2 installs without any trouble in a new conda environment. I made this environment with mamba create --name cppyy python=3.10 awkward uproot vector numba compilers cmake make to control which compilers are visible in the environment—a suite from conda-forge and not from system paths. ( So that's great! |
Hi, sorry to report this! I tried installing from source using the instructions in
https://cppyy.readthedocs.io/en/latest/installation.html#install-from-source
I'm in a new conda environment with no ROOT in my environment. These are the packages:
(All of my compilers come from conda.)
Here's the output from the pip-install from source:
Incidentally, the symbol that it can't find from libCling.so is
TClassEdit::TInterpreterLookupHelper
, though that's probably just the first in what it's looking for.@vgvassilev thinks it could have something to do with rtti.
The text was updated successfully, but these errors were encountered: