Closed swertz closed 2 years ago
I can't reproduce easily so that makes me think it might be an environment issue:
env
?root=6.24.6
work for you?(FYI: Using mamba install
instead of conda install
is considerably faster, see the link for details?)
I've tried with root=6.24.6
in a new environment and that works fine!
(root624) swertz@swertz-thinkpad ~ root
root [0] gROOT->GetVersion()
(const char *) "6.24/06"
Here is a dump of my environment (after activating the conda env): env.txt
I don't see anything obviously problematic, apart from /home/swertz/.local/bin
appearing in the PATH
: there is some python stuff in there that could create conflicts - not sure how it got there - but it's located after the conda paths in PATH
anyway.
(FYI: Using mamba install instead of conda install is considerably faster, see the link for details?)
Thanks, forgot about that!
Thanks @swertz for the help debugging. It turns out it's caused by the leading .
in the miniconda directory which cause's ROOT's path resolution to fail.
The fix is in: https://github.com/root-project/root/pull/10073
Solution to issue cannot be found in the documentation.
Issue
I have successfully installed ROOT 6.26 in a miniconda environment using:
However, it is not possible to launch
root
or any root-based command (rootbrowse
etc.); it crashes with:I should note that there is no such folder as
/home/swertz/.miniconda3/envs/root626/include/llvm
!Installed packages
Environment info