You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I got kernel inside Jupyter but it dies immediately. As far as i understood, the earlier issues solved with an update and there is no similar problems. Here is the error:
It seemes like the file doesn't even created in .../cling-build/lib/. So, I don't think it's about not finding the file. When I ran make command inside .../cling-build/tools/cling/tools/Jupyter, it solved the issue. Now, I have .../cling-build/lib/libclingJupyter.so and works fine.
I didn't get any error while linking and my consecutive runs didn't changed anything. Maybe important point, I learnt that I need to run first after my first error cmake --build . --target clang. However, I also ran cmake --build . --target cling afterwards so I don't think this is the issue.
I'm on fedora 40 and ran soft linked directory from another drive if it helps.
The text was updated successfully, but these errors were encountered:
After using these commands, cling works as expected.
However when I run these instructions for Jupyter support
I got kernel inside Jupyter but it dies immediately. As far as i understood, the earlier issues solved with an update and there is no similar problems. Here is the error:
It seemes like the file doesn't even created in
.../cling-build/lib/
. So, I don't think it's about not finding the file. When I ranmake
command inside.../cling-build/tools/cling/tools/Jupyter
, it solved the issue. Now, I have.../cling-build/lib/libclingJupyter.so
and works fine.I didn't get any error while linking and my consecutive runs didn't changed anything. Maybe important point, I learnt that I need to run first after my first error
cmake --build . --target clang
. However, I also rancmake --build . --target cling
afterwards so I don't think this is the issue.I'm on fedora 40 and ran soft linked directory from another drive if it helps.
The text was updated successfully, but these errors were encountered: