-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Installation failure #8
Comments
@adamaequo Hi, thanks for reporting the issue. Hmm... do you happen to have ROOT installed on your computer? Their rootcling installation would clash and produce weird outputs. |
As far as I am aware of, no. I tested it with:
|
Thanks, may you share the version of cppyy, gcc and python you are using? |
|
cppyy 2.0.0 has Cling based on Clang9, the options parser of which has changed: options that are not recognized are no longer send into a "sink" option if part of the option is recognized. That is "-std=c++1z" is parsed as "-s td=c++1z" b/c the "-s" is a valid option. Similar for "-f". To pass extra CLI arguments to Cling, underlying rootcling, use the Note that that syntax is compatible with cppyy 1.x, as the |
@wlav Thanks for helping! There seems to be problem with the new cling. It seems to be stuck in an infinite recursion. I think I've seen this behavior before cppyy 2.0. But ignored it since I can fallback to a old cppyy.
I tried to debug this myself. But it's way too out of my capabilities. ROOT 6.24 seem to be able to handle the library just fine. Should I open a bug in cppyy? |
If it's standalone reproducible, then sure. |
Hey, I tried to install PyEtaler on a ubuntu20.04, and so far all 3 methods failed, because of the same error.
I successfully installed Etaler, and was able to run the examples, but no luck getting PyEtaler to work so far.
Here is the full log of executing the command: "python3 genbinding.py" https://pastebin.com/24K4H0mP
If I run the rootcling command on its own, I get:
To me it seems like this error occurs because "-std=c++1z" is a -s option and "-fsigned-char" a -f option...
The text was updated successfully, but these errors were encountered: